bootstd: Scanning for USB bootflow will remove existing SCSI bootflow
Tony Dinh
mibodhi at gmail.com
Mon Oct 2 21:25:53 CEST 2023
Hi Simon,
On Sun, Oct 1, 2023 at 6:22 PM Simon Glass <sjg at chromium.org> wrote:
>
> Hi Tony,
>
> On Tue, 26 Sept 2023 at 13:40, Tony Dinh <mibodhi at gmail.com> wrote:
> >
> > Hi Simon,
> >
> > On Tue, Sep 26, 2023 at 4:37 AM Simon Glass <sjg at chromium.org> wrote:
> > >
> > > Hi Tony,
> > >
> > > On Mon, 25 Sept 2023 at 14:02, Tony Dinh <mibodhi at gmail.com> wrote:
> > > >
> > > > Hi Simon,
> > > >
> > > > Here is an observation during testing the bootflow command.
> > > >
> > > > If there is a SCSI bootflow, scanning for USB bootflow will remove that existing
> > > > SCSI bootflow. To bring it back, I scanned for SCSI bootflow again, and it was
> > > > back to normal. Perhaps there is some kind of indexing problem?
> > >
> > > Yes that's right. The 'botflow scan' command is not additive. The
> > > first thing it does is removing existing bootflows.
> >
> > Thanks for clarifying that. I assumed it is additive, because the
> > existing USB bootflow was not removed when I did a "bootflow scan
> > scsi" immediately after (see the end of the log).
>
> Yes, but I'm not sure what is going on there. Perhaps it is a bug?
> When you scan SCSI it should not also scan USB.
Yes, it looks like a bug. I think I can see the problem and am working
on a patch.
All the best,
Tony
>
> Regards,
> SImon
More information about the U-Boot
mailing list