[PATCH v1 1/1] include: configs: tegra-common-post: make usb first boot target

[Svyatoslav Ryhel]

вт, 18 черв. 2024 р. о 17:16 Svyatoslav <clamor95 at gmail.com> пише:
>
>
>
> 18 червня 2024 р. 15:23:09 GMT+03:00, Thierry Reding <treding at nvidia.com> написав(-ла):
> >On Tue Jun 18, 2024 at 2:00 PM CEST, Svyatoslav Ryhel wrote:
> >> This ensures that the device can boot from a USB device prior to MMC. Useful
> >> cases are when installing a new OS from USB while MMC still has a working OS
> >> configuration or if the OS configuration is broken in late boot stages
> >> (kernel boots but the system does not start).
> >>
> >> Signed-off-by: Svyatoslav Ryhel <clamor95 at gmail.com>
> >> ---
> >>  include/configs/tegra-common-post.h | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >What's the implication of this if no USB mass storage device is found?
> >How does this behave when USB cannot be read or booting from it doesn't
> >work?
> >
> >I vaguely recall that boot order doesn't always proceed, though
> >admittedly I haven't tested all of these edge-cases in a long time.
> >
> >Thierry
>
> If no USB mass storage is found bootflow will continue with the next
> device in the list (mmc1) with co-responding info that booting from
> usb failed. I have tested this on lg p895 which has only mmc0 and
> with asus transformers which have usb, mmc0 and mmc1 in all
> possible configurations. I did not have booting issues whatsoever.
> ATM, transformers use boot order which I have proposed in this
> commit.
>
> Best regards,
> Svyatoslav R.

Thierry,

Since you have not responded to my statement above I assume that
you are fine with applying this change. In case you have any
objections please answer as soon as you can since I am planning to
include it into merge request for the next merge window.

Best regards,
Svyatoslav R.