From: Benson Leung <bleung@chromium.org>
To: Andrew Chant <achant@google.com>
Cc: Benson Leung <bleung@chromium.org>,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, bleung@google.com
Subject: Re: [PATCH] USB: announce bcdDevice as well as idVendor, idProduct.
Date: Fri, 23 Mar 2018 18:34:05 -0700 [thread overview]
Message-ID: <20180324013405.GA230543@decatoncale.mtv.corp.google.com> (raw)
In-Reply-To: <CANVWZtGS9x-zLAgtV0rkgnBR0kLHTT0LYjKEreNy6qjkcC75PA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On Fri, Mar 23, 2018 at 06:08:07PM -0700, Andrew Chant wrote:
> >> + "New USB device found, idVendor=%04x, idProduct=%04x, bcdDevice=%04x\n",
> > Can you please decode bcdDevice into a decimal string?
> >
> > lsusb -v does this (bcdDevice: 0.03 for example) and in my experience
> > it has generally matched up with how hardware manufacturers refer
> > to their firmware.
>
> Nevermind, %x should show bcd properly. looks fine.
I like the way lsusb -v does it better. Take a look at v2.
Thanks,
Benson
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-24 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 0:33 Benson Leung
2018-03-24 0:48 ` Andrew Chant
2018-03-24 1:08 ` Andrew Chant
2018-03-24 1:34 ` Benson Leung [this message]
2018-03-24 1:31 ` [PATCH v2] " Benson Leung
2018-03-24 16:06 ` Alan Stern
2018-03-24 17:43 ` Benson Leung
2018-03-24 17:40 ` [PATCH v3] " Benson Leung
2018-03-26 18:27 ` Alan Stern
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=20180324013405.GA230543@decatoncale.mtv.corp.google.com \
--to=bleung@chromium.org \
--cc=achant@google.com \
--cc=bleung@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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
Powered by JetHome