Re: Re bootstd: Skip over bad device during bootflows scanning
Hi Simon, On Tue, Oct 31, 2023 at 12:00 PM Tony Dinh wrote: > > Hi Simon, > > On Tue, Oct 31, 2023 at 11:50 AM Simon Glass wrote: > > > > Hi Tony, > > > > Sorry I cannot reply to the patch[1]. > > > > Can you please send the console trace for this situation? I don't want > > to ignore errors completely, so wonder if there is a special error > > code which could be produced when a device is missing? > > The error is -ENOSYS (-38). But sure, I'll post the console log. I've sent the console log in the patch thread. All the best, Tony
Re: Re bootstd: Skip over bad device during bootflows scanning
Hi Simon, On Tue, Oct 31, 2023 at 11:50 AM Simon Glass wrote: > > Hi Tony, > > Sorry I cannot reply to the patch[1]. > > Can you please send the console trace for this situation? I don't want > to ignore errors completely, so wonder if there is a special error > code which could be produced when a device is missing? The error is -ENOSYS (-38). But sure, I'll post the console log. Thanks, Tony > > Regards, > Simon > > [1] > https://patchwork.ozlabs.org/project/uboot/patch/20231030194650.11594-1-mibo...@gmail.com/
Re bootstd: Skip over bad device during bootflows scanning
Hi Tony, Sorry I cannot reply to the patch[1]. Can you please send the console trace for this situation? I don't want to ignore errors completely, so wonder if there is a special error code which could be produced when a device is missing? Regards, Simon [1] https://patchwork.ozlabs.org/project/uboot/patch/20231030194650.11594-1-mibo...@gmail.com/