> * architecture support can't be added to arch/ because that contains> code for CPUs not code that is about helping to support multiple CPUs.> eoma isn't a CPU.

See above.. it's a bus

> very basic question. where the hell should EOMA support source code go?> > bearing in mind that the first CPU card is an Allwinner A10, the next> one is likely to be an AMD Fusion, the one after that could be from> icubecorp, the one after that a multi-core SMP xtensa, etc.

Off the top of my head I suspect you want

drivers/eoma68/

which is the bus interface and glue including reading the device treedata for the current board you are plugged into and building a devicetree from that.

lib/eoma68

or some similar name, which is the library routines everything usingeoma68 needs

arch/[x86.arm,..]/platform/eoma68/..

probably the platform code for each system.

I don't btw see the problem with your device trees and display. If you'vegot a device tree on *both* the CPU card and the I/O boards then you'vegot all the data in the right places.