From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb: create common header virtual root hub descriptors
Date: Fri, 14 Feb 2014 09:23:40 +0100 [thread overview]
Message-ID: <201402140923.40091.marex@denx.de> (raw)
In-Reply-To: <52FD98BA.8010504@wwwdotorg.org>
On Friday, February 14, 2014 at 05:16:58 AM, Stephen Warren wrote:
> On 02/13/2014 01:44 PM, Marek Vasut wrote:
> > On Thursday, February 13, 2014 at 06:42:18 AM, Stephen Warren wrote:
> >> Many USB host controller drivers contain almost identical copies of the
> >> same virtual root hub descriptors. Put these into a common file to avoid
> >> duplication.
> >>
> >> Note that there were some very minor differences between the descriptors
> >> in the various files, such as:
> >>
> >> - USB 1.0 vs. USB 1.1
> >> - Manufacturer/Device ID
> >> - Max packet size
> >> - String content
> >>
> >> I assume these aren't relevant.
> >
> > Please CC the driver authors so we can be sure.
>
> OK, I've done so. It's pretty unclear who the relevant driver authors or
> maintainers are for most of the files, so I cast a wide net from git
> log, doc/git-mailrc, and (c) messages in the file. I don't expect the
> message to make it to the list because of the Cc count. I doubt many
> people will respond.
>
> I hoped this would be the kind of call you could make yourself as the
> USB stack maintainer.
Sorry, I cannot. I have no clue about _all_ the hardware out there. That's why I
want opinion of the hardware maintainers.
Best regards,
Marek Vasut
prev parent reply other threads:[~2014-02-14 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 5:42 [U-Boot] [PATCH] usb: create common header virtual root hub descriptors Stephen Warren
2014-02-13 20:44 ` Marek Vasut
2014-02-14 4:16 ` Stephen Warren
2014-02-14 8:23 ` Marek Vasut [this message]
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=201402140923.40091.marex@denx.de \
--to=marex@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox