From: Sascha Hauer <s.hauer@pengutronix.de>
To: Christian Eggers <ceggers@arri.de>
Cc: barebox@lists.infradead.org, Primoz Fiser <primoz.fiser@norik.com>
Subject: Re: Some USB memory sticks not (fully) recognized
Date: Mon, 10 Aug 2020 21:26:43 +0200 [thread overview]
Message-ID: <20200810192643.GB31536@pengutronix.de> (raw)
In-Reply-To: <3346214.S29caFStrp@n95hx1g2>
Hi Christian,
On Mon, Aug 10, 2020 at 01:52:01PM +0200, Christian Eggers wrote:
> On Thursday, 6 August 2020, 16:29:13 CEST, Christian Eggers wrote:
> > Barebox version: 2020.07.0
> > Hardware: i.MX6 ULL with external Microchip USB Hub attached
> >
> > I got a bug report that some newer USB memory sticks do not work with
> > barebox. While with barebox-2020.01 these devices are not recognized at all,
> > in barebox-2020.07 I get at least some warnings:
> I checked again with an older release of barebox (2019-06). With this version,
> the USB drive is detected:
>
> > # usb -s
> > usb: USB: scanning bus for devices...
> > usb: Bus 001 Device 001: ID 0000:0000 EHCI Host Controller
> > usb: Bus 001 Device 002: ID 0424:4916 USB4916
> > usb: Bus 001 Device 003: ID 090c:3267 Flash Disk
> > Using index 0 for the new disk
> > usb: Bus 001 Device 004: ID 0424:494a USB2 Controller Hub
> > usb: 4 USB Device(s) found
> > Bus 001 Device 001: ID 0000:0000 EHCI Host Controller
> > Bus 001 Device 002: ID 0424:4916 USB4916
> > Bus 001 Device 003: ID 090c:3267 Flash Disk
> > Bus 001 Device 004: ID 0424:494a USB2 Controller Hub
>
> Also mounting the drive works fine. So I guess that this problem may have been
> introduced here:
>
> b1d9837182 ("usb: Change power-on / scanning timeout handling")
Before guessing further could you verify that exactly this commit breaks
your setup? There are a few more changes in the area that could be the
culprit.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-08-10 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 14:29 Christian Eggers
2020-08-10 11:52 ` Christian Eggers
2020-08-10 19:26 ` Sascha Hauer [this message]
2020-08-11 6:10 ` Christian Eggers
2020-08-11 6:33 ` Sascha Hauer
2020-08-12 8:35 ` [PATCH] Revert "usb: host: ehci: Use to USBSTS to wait for transfer completion" Christian Eggers
2020-08-14 13:21 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200810192643.GB31536@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ceggers@arri.de \
--cc=primoz.fiser@norik.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox