From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] mx6ul_14x14_evk: Remove CONFIG_SPL_FAT_SUPPORT
Date: Sun, 13 Sep 2015 10:54:10 +0200 [thread overview]
Message-ID: <55F539B2.7010600@denx.de> (raw)
In-Reply-To: <CAOMZO5Bv14EhSTq3-vYW5FJhAuZoey9NHz1VkK7rZBngezEELg@mail.gmail.com>
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.
>
Most of us agree to unify i.MX boards using storing the bootloader as
raw data.
Applied to u-boot-imx, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2015-09-13 8:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 17:43 [U-Boot] [PATCH 1/4] thermal: imx_thermal: Do not print on error Fabio Estevam
2015-09-08 17:43 ` [U-Boot] [PATCH 2/4] imx-common: cpu: Do not print on invalid temperature Fabio Estevam
2015-09-08 17:43 ` [U-Boot] [PATCH 3/4] mx6ul_14x14_evk: Remove CONFIG_SPL_FAT_SUPPORT Fabio Estevam
2015-09-09 3:29 ` Peng Fan
2015-09-09 7:37 ` Stefano Babic
2015-09-09 12:26 ` Fabio Estevam
2015-09-09 12:45 ` Otavio Salvador
2015-09-09 13:36 ` Stefano Babic
2015-09-09 13:33 ` Peng Fan
2015-09-09 15:47 ` Fabio Estevam
2015-09-13 8:54 ` Stefano Babic [this message]
2015-09-08 17:43 ` [U-Boot] [PATCH 4/4] mx6ul_14x14_evk: Add a README file Fabio Estevam
2015-09-13 8:50 ` [U-Boot] [PATCH 1/4] thermal: imx_thermal: Do not print on error Stefano Babic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55F539B2.7010600@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.