On 9/21/2012 11:21 PM, Dirk Behme wrote:
Hi Troy,
On 22.09.2012 04:38, Troy Kisky wrote:
After this series the same binary will run on a
Saberlite board using any of the pin compatible processors
mx6 quad, mx6 duallite, or mx6 solo. This is accomplished
using a plugin and a table built by mkimage.
Could you briefly explain or give a link to some documentation how
this does work? It sounds to me that the plugin concept is something
the boot ROM has to understand? Or in other words: How does the boot
ROM decide on which processor it runs and which DCD table to execute
then?
Sorry if I misunderstood something, I'm not so familiar with the boot
ROM options.
Many thanks
Dirk
The table generated by mkimage for use with the plugin is not a standard
ROM decodable table.
Only the plugin itself will decode the table. After it processes the
table to initialize memory,
it calls back into the ROM to finish the u-boot load.
see file arch/arm/include/asm/arch-mx6/imx-mkimage.h
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
