[OE-core] Going beyond MACHINE?

[Mike Looijmans]

The short version of my question: Can I define a "level" that goes beyond MACHINE?

My problem in detail (and I suspect there are more systems with similar problems):

I have an SOC called "topic-miami". There are currently two variants: The 7015 
and 7030. They are identical but for one component: They have a different FPGA 
part (the 7030 is bigger and faster).
Both run exactly the same kernel and bootloader, and all other software and 
libraries are exactly the same.

Currently I have MACHINE="topic-miami-7015" and then SOC_FAMILY="topic-miami" 
so I can use "topic-miami" as override word for all packages.

However, this means I get two kernels, two bootloaders, etc. even though they 
are exactly the same.

The only package that currently differs is the one that delivers the 
bitstream(s) for the FPGA. These are big, too big to fit bitstreams for both 
models into flash and leave room for applications, so just installing both 
into the rootfs and pick the correct one at boot time is not really an option.

Maybe I could define some extra PACKAGE_ARCH for the bitstreams (which make 
sense, as this is sort of firmware for a different platform). But how would a 
user then pick the right value for this variable, since MACHINE seems to be 
the only thing he can really choose?

Any thoughts and ideas are welcome...


Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans at topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/