Hi Fabio,
On 09/09/2015 14:26, Fabio Estevam wrote:
Hi Peng and Stefano,
On Wed, Sep 9, 2015 at 4:37 AM, Stefano Babic sbabic@denx.de wrote:
#define CONFIG_SPL_LIBCOMMON_SUPPORT #define CONFIG_SPL_MMC_SUPPORT -#define CONFIG_SPL_FAT_SUPPORT
Can we keep this? Without this, we need to burn u-boot.img into sdcard, but i prefer to load u-boot.img from the fat partition.
Well, how U-Boot is stored on the SD-Card is a decision that you take based on the balance safety against comfortably. Both are ok on my side. If we put u-boot.img in raw SD at a fixed address, it is very uncommon that a user destroy accessing it. On the other side, putting it into a FAT partition makes easier to update for everybody - just copying it into a disk. The issue reported by Fabio is like a corrupted SD-Card - the SD-Card does not contain the correct bootloader and it is ok if it does not boot or hangs. Both ways have advantages and disadvantages.
I am trying to get this more standard across Freescale boards.
Like it was pointed out here: http://lists.denx.de/pipermail/u-boot/2015-August/222061.html
I think it can be confusing for the end user if each FSL board has a different way for booting u-boot.img, so that's why I chose the common approach here.
Absolutely - the user will be confused. I am fine with any decision you take on that sense. IMHO in Freescale's boards (I mean, since MX51 and later) has always written u-boot in raw mode. My vote goes for removing the flag, then.
Regards, Stefano Babic