From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Kocialkowski Date: Wed, 26 Aug 2015 13:00:01 +0200 Subject: [U-Boot] [PATCH] omap-common: SYS_BOOT fallback logic correction In-Reply-To: <55DD5B96.5030406@schmelzer.or.at> References: <1440517253-18394-1-git-send-email-contact@paulk.fr> <55DD5B96.5030406@schmelzer.or.at> Message-ID: <1440586801.2524.26.camel@collins> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: This is a digitally signed message part URL: