On 6/20/23 12:43, Xavier Drudis Ferran wrote:
El Tue, Jun 20, 2023 at 11:49:36AM +0200, Marek Vasut deia:
Default, see:
$ git grep CONFIG_BOOTCOMMAND configs/
I'm lost.
I called default what Kconfig used as default.
You seem to call default what's in board specific config files.
Whatever. F
On Tue, 20 Jun 2023 at 12:20, Xavier Drudis Ferran wrote:
>
> El Tue, Jun 20, 2023 at 11:03:57AM +0100, Simon Glass deia:
> > Hi Xavier,
> >
>
> Hi Simon,
>
> > >
> > > It is also possible that one day a device that is not UCLASS_BLK,
> > > UCLASS_BOOTDEV or UCLASS_USB_EMUL is put as children of a
El Tue, Jun 20, 2023 at 11:03:57AM +0100, Simon Glass deia:
> Hi Xavier,
>
Hi Simon,
> >
> > It is also possible that one day a device that is not UCLASS_BLK,
> > UCLASS_BOOTDEV or UCLASS_USB_EMUL is put as children of a usb storage
> > device (just imagine a future system similar to bootstd for
El Tue, Jun 20, 2023 at 11:49:36AM +0200, Marek Vasut deia:
>
> Default, see:
> $ git grep CONFIG_BOOTCOMMAND configs/
>
I'm lost.
I called default what Kconfig used as default.
You seem to call default what's in board specific config files.
Whatever. Fix the wording in the commit message if you
Hi Xavier,
On Wed, 14 Jun 2023 at 09:40, Xavier Drudis Ferran wrote:
>
>
> Thanks for explaining, Simon Glass.
>
> Can someone please stop me if I'm splitting hairs or bikeshedding or
> something ? I guess we agree both checking for null or UCLASS_BOOTDEV
> would work right now but we are looking
On 6/20/23 09:03, Xavier Drudis Ferran wrote:
El Tue, Jun 20, 2023 at 02:50:48AM +0200, Marek Vasut deia:
On 6/13/23 08:52, Xavier Drudis Ferran wrote:
U-Boot TPL 2023.07-rc2-00144-g497967f1ee (Jun 12 2023 - 11:15:47)
Next is already at rc4 , what's this rc2 ?
It's a test I did last week (
El Tue, Jun 20, 2023 at 02:50:48AM +0200, Marek Vasut deia:
> On 6/13/23 08:52, Xavier Drudis Ferran wrote:
> >
> > U-Boot TPL 2023.07-rc2-00144-g497967f1ee (Jun 12 2023 - 11:15:47)
>
> Next is already at rc4 , what's this rc2 ?
It's a test I did last week (June 12th). What do you think has chan
On 6/13/23 08:52, Xavier Drudis Ferran wrote:
Ok. New test.
This uses yesterday morning's next branch.
commit 5b589e139620214f
Merge: cc5a940923 32d2461e04
Merge branch 'next_net/phy_connect_dev'
USB2 does not work for rk3399 in next (fixes are in master, thanks),
but USB3 is enough.
I com
Thanks for explaining, Simon Glass.
Can someone please stop me if I'm splitting hairs or bikeshedding or
something ? I guess we agree both checking for null or UCLASS_BOOTDEV
would work right now but we are looking for what's more future-proof.
El Tue, Jun 13, 2023 at 09:12:30PM +0100, Simon Gl
Hi Xavier,
On Tue, 13 Jun 2023 at 17:04, Xavier Drudis Ferran wrote:
>
> El Tue, Jun 13, 2023 at 03:58:22PM +0100, Simon Glass deia:
> >
> > Yes that's right. So 'usb info' should ignore UCLASS_BOOTDEV devices.
>
> That's a possibility, yes. It should work until someone adds another
> device ther
El Tue, Jun 13, 2023 at 03:58:22PM +0100, Simon Glass deia:
>
> Yes that's right. So 'usb info' should ignore UCLASS_BOOTDEV devices.
That's a possibility, yes. It should work until someone adds another
device there for some other purpose.
> That is better than checking for the NULL pointer.
>
Hi Xavier,
On Tue, 13 Jun 2023 at 07:52, Xavier Drudis Ferran wrote:
>
> Ok. New test.
>
> This uses yesterday morning's next branch.
> commit 5b589e139620214f
> Merge: cc5a940923 32d2461e04
> Merge branch 'next_net/phy_connect_dev'
>
> USB2 does not work for rk3399 in next (fixes are in mast
Ok. New test.
This uses yesterday morning's next branch.
commit 5b589e139620214f
Merge: cc5a940923 32d2461e04
Merge branch 'next_net/phy_connect_dev'
USB2 does not work for rk3399 in next (fixes are in master, thanks),
but USB3 is enough.
I compiled for rock-pi-4-rk3399_defconfig
flashed to
El Mon, Jun 12, 2023 at 10:17:38PM +0100, Simon Glass deia:
>
> I'm not sure what is going on here. Which version are you testing? Do
> you have these two commits?
>
> 8c29b73278d6 bootstd: usb: Avoid initing USB twice
> 9fea3a799dde usb: Tidy up the usb_start flag
>
> Regards,
> Simon
Yes, I h
Hi,
On Sun, 11 Jun 2023 at 13:29, Marek Vasut wrote:
>
> On 6/9/23 20:52, Xavier Drudis Ferran wrote:
> > Sorry, I replied to Marek only but meant to reply to all.
> >
> > El Fri, Jun 09, 2023 at 03:20:33AM +0200, Marek Vasut deia:
> >
> >>> No. Well, in some tests yes and some no, but I got the
On 6/9/23 20:52, Xavier Drudis Ferran wrote:
Sorry, I replied to Marek only but meant to reply to all.
El Fri, Jun 09, 2023 at 03:20:33AM +0200, Marek Vasut deia:
No. Well, in some tests yes and some no, but I got the error in all cases.
This is doubtful. It is mandatory to run 'usb start' o
Sorry, I replied to Marek only but meant to reply to all.
El Fri, Jun 09, 2023 at 03:20:33AM +0200, Marek Vasut deia:
> > No. Well, in some tests yes and some no, but I got the error in all cases.
>
> This is doubtful. It is mandatory to run 'usb start' or 'usb reset' before
> you would get any
17 matches
Mail list logo
