From: DATACOM - Paulo.Zaneti <paulo.zaneti@datacom.com.br>
To: u-boot@lists.denx.de
Subject: [U-Boot] usb: Fail to get descriptor for USB 2.0 device
Date: Wed, 23 May 2018 14:52:09 -0300 [thread overview]
Message-ID: <2dc64c17-6d54-2d50-2050-0b4dd6a731d8@datacom.com.br> (raw)
In-Reply-To: <d510df0c-4df3-9425-4112-243db80cdce2@denx.de>
On 23/05/2018 14:43, Marek Vasut wrote:
> On 05/23/2018 07:37 PM, DATACOM - Paulo.Zaneti wrote:
>>
>> On 23/05/2018 14:03, Marek Vasut wrote:
>>> On 05/23/2018 07:00 PM, DATACOM - Paulo.Zaneti wrote:
>>>> Hi,
>>> Hi,
>>>
>>>> When trying to migrate a board from u-boot version 2016.09 to version
>>>> 2018.03, I found a problem with a USB 2.0 device which used to work on
>>>> version 2016.09.
>>> Does it still happen in u-boot/master ?
>> Yes, it still happens.
>>
>> I just tested it with the following commit:
>> dca268a .travis.yml: Further optimizations
>>>> In u-boot version 2016.09 the device appears like this:
>>>>
>>>> 2: Mass Storage, USB Revision 2.0
>>>> - SanDisk Cruzer Blade 200443243002FB509E64
> Let me guess, is this a DWC2-based host ? You didn't mention which SoC
> or USB controller it is.
>
> Cfr https://lists.denx.de/pipermail/u-boot/2016-January/240090.html ,
> DWC2 has problems with those sandisk sticks.
No, it is a NXP T1024 SoC.
Do you think it may be a problem with the SoC or NXP USB host driver ?
next prev parent reply other threads:[~2018-05-23 17:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 17:00 [U-Boot] usb: Fail to get descriptor for USB 2.0 device DATACOM - Paulo.Zaneti
2018-05-23 17:03 ` Marek Vasut
2018-05-23 17:37 ` DATACOM - Paulo.Zaneti
2018-05-23 17:43 ` Marek Vasut
2018-05-23 17:52 ` DATACOM - Paulo.Zaneti [this message]
2018-05-23 18:00 ` Marek Vasut
2018-05-23 20:51 ` DATACOM - Paulo.Zaneti
2018-05-23 21:50 ` Marek Vasut
2018-05-23 23:40 ` Bin Meng
2018-05-24 16:23 ` DATACOM - Paulo.Zaneti
2018-05-24 17:57 ` Marek Vasut
2018-05-24 22:13 ` DATACOM - Paulo.Zaneti
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=2dc64c17-6d54-2d50-2050-0b4dd6a731d8@datacom.com.br \
--to=paulo.zaneti@datacom.com.br \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.