[OE-core] Setting a preferred provider via image?

Mike Looijmans mike.looijmans at topic.nl
Thu Feb 20 07:51:44 UTC 2014


I've gotten into a jam now.

For an image to work nicely on a Zynq processor, it needs to load the FPGA 
with useful stuff, and it also needs to adapt the (SPL) bootloader to 
configure the clocks etcetera at boot.

The FPGA image recipe yields "ps7_init.[ch]" files which must be compiled into 
u-boot, and which are to be created usin Xilinx tools.

For now, I've invented a "virtual/xilinx-sdk" package that can be provided by 
the FPGA recipe, and u-boot-spl that DEPENDS on it. In the machine or local 
config, one can set PREFERRED_PROVIDER_virtual/xilinx-sdk="package" and thus 
pick the FPGA design that will be responsible for the bootloader.

My problem now is that the FPGA configuration is actually something that the 
"image" decides upon, and multiple configurations can be used for a single 
machine (great all programmable hardware) because the FPGA part can implement 
just about anything (and switch that at runtime too).

Is there a way to propagate a PREFERRED_PROVIDER via the image?

Or shoud I move in another direction and consider a slightly differently 
configured FPGA as a totally new MACHINE? Maybe use MACHINE_CLASS to join them?

I'm interested in your ideas, opinions, tricks, etc...


-- 
Mike Looijmans - TOPIC Automation


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

Dit e-mail bericht en de eventueel daarbij behorende bijlagen zijn uitsluitend bestemd voor de geadresseerde, zoals die blijkt uit het e-mail bericht en/of de bijlagen. Er kunnen gegevens met betrekking tot een derde instaan. Indien u als niet-geadresseerde dit bericht en de bijlagen ontvangt, terwijl u niet bevoegd of gemachtigd bent om dit bericht namens de geadresseerde te ontvangen, wordt u verzocht de afzender hierover direct te informeren en het e-mail bericht met de bijlagen te vernietigen. Ieder gebruik van de inhoud van het e-mail bericht, waaronder de daarbij behorende bijlagen, door een ander dan de geadresseerde is onrechtmatig jegens ons dan wel de eventueel in het e-mail bericht of de bijlagen voorkomende andere personen. TOPIC Embedded Systems is niet aansprakelijk voor enigerlei schade voortvloeiend uit het gebruik en/of acceptatie van dit e-mail bericht of de daarbij behorende bijlagen.

The contents of this message, as well as any enclosures, are addressed personally to, and thus solely intended for the addressee. They may contain information regarding a third party. A recipient who is neither the addressee, nor empowered to receive this message on behalf of the addressee, is kindly requested to immediately inform the sender of receipt, and to destroy the message and the enclosures. Any use of the contents of this message and/or the enclosures by any other person than the addressee or person who is empowered to receive this message, is illegal towards the sender and/or the aforementioned third party. TOPIC Embedded Systems is not  liable for any damage as a result of the use and/or acceptance of this message and as well as any enclosures.



More information about the Openembedded-core mailing list