By the way, would you like to add am33xx support to the SYS_BOOT-based fallback interface?
There is already get_sysboot_value on am33xx code (that is unused), I suggest that you use that function to write a proper omap_sys_boot_device in boot.c, as is done on omap platforms (and get rid of get_sysboot_value afterwards). Most of the work is to fill up a boot_devices array to match up each first *memory* booting devices based on the SYS_BOOT value, for each supported platform. Currently, am33xx supports: * AM33xx * AM43xx * TI81xx: TI816x (DM816x/AM389x), TI814x (DM814x/AM387x) That's 4 platforms and 4 TRMs to get the data from. The list of proper CONFIG defines to each for each platform can be found in arch/arm/includes/asm/arch-am33xx/spl.h Let me know if you're interested, I didn't do it at first because I have no device to test this with. -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security. Website: http://www.replicant.us/ Blog: http://blog.replicant.us/ Wiki/tracker/forums: http://redmine.replicant.us/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
