Hi Simon,
On Wed, Nov 1, 2023 at 9:10 AM Simon Glass wrote:
>
> Hi Tony,
>
> On Tue, 31 Oct 2023 at 13:45, Tony Dinh wrote:
> >
> > On Tue, Oct 31, 2023 at 12:26 PM Tony Dinh wrote:
> > >
> > > Hi Simon,
> > >
> > > On Mon, Oct 30, 2023 at 12:47 PM Tony Dinh wrote:
> > > >
> > > > During
Hi Tony,
On Tue, 31 Oct 2023 at 13:45, Tony Dinh wrote:
>
> On Tue, Oct 31, 2023 at 12:26 PM Tony Dinh wrote:
> >
> > Hi Simon,
> >
> > On Mon, Oct 30, 2023 at 12:47 PM Tony Dinh wrote:
> > >
> > > During scanning for the next bootdev, if bootdev_next_prio() encounters
> > > a device error
On Tue, Oct 31, 2023 at 12:26 PM Tony Dinh wrote:
>
> Hi Simon,
>
> On Mon, Oct 30, 2023 at 12:47 PM Tony Dinh wrote:
> >
> > During scanning for the next bootdev, if bootdev_next_prio() encounters
> > a device error (e.g. ENOSYS), let it continue scanning the next devices,
> > not stopping
Hi Simon,
On Mon, Oct 30, 2023 at 12:47 PM Tony Dinh wrote:
>
> During scanning for the next bootdev, if bootdev_next_prio() encounters
> a device error (e.g. ENOSYS), let it continue scanning the next devices,
> not stopping prematurely.
>
> Background:
>
> During scanning for bootflows, it's
During scanning for the next bootdev, if bootdev_next_prio() encounters
a device error (e.g. ENOSYS), let it continue scanning the next devices,
not stopping prematurely.
Background:
During scanning for bootflows, it's possible for bootstd to encounter a
faulty device controller. Also when the
5 matches
Mail list logo