On Wed, Apr 03, 2019 at 02:59:28PM +0530, Faiz Abbas wrote: > Hi Sam, > > On 29/03/19 8:37 PM, Sam Protsenko wrote: > > Hi Faiz, > > > > On Fri, Mar 29, 2019 at 3:24 PM Lokesh Vutla <lokeshvu...@ti.com> wrote: > >> > >> + Praneeth > >> > >> On 29/03/19 4:45 PM, Tom Rini wrote: > >>> On Fri, Mar 29, 2019 at 01:09:25PM +0530, Faiz Abbas wrote: > >>>> Tom, > >>>> > >>>> On 28/03/19 6:33 PM, Tom Rini wrote: > >>>>> On Thu, Mar 28, 2019 at 02:21:03PM +0530, Faiz Abbas wrote: > >>>>> > >>>>>> With U-boot supporting environment in multiple places, enable only > >>>>>> ENV_IS_IN_EMMC. > >>>>>> > > > > Can you please describe in more details, which exactly problem you are > > trying to fix in this patch? As I understand, we support SD boot in > > Linux SDK [1], so saving env in FAT can be useful in this case. Could > > this issue be fixed in some other way, rather than dropping > > multi-environment feature? > > > > Thanks! > > Today U-boot comes up and always looks for environment first in SD Fat > partition and then in the eMMC. We should not allow U-boot to look for > environment in every single boot media that is enabled. We have had a > policy of saving environment in eMMC since a long time (before the > multi-environment feature was added) even when booting from SD card. I > know that most people would prefer it to be in SD card but because of > android requirements, we chose it to be in eMMC. > > Furthermore, the error message when it looks for environment in SD card > and fails is an invitation for trouble from users (even more so when > there is a confusion regarding where the environment should be and how > to change it).
Maybe this is motivation to implement some of the ideas (or propose a new one) for "make env not found on X trying Y" less scary and/or something other than link order for order we look for environment in. -- Tom
signature.asc
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
