All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Stratton Treadway <vgerlists@nathanst.com>
To: linux-usb@vger.kernel.org
Subject: Re: Adding "UAS" protocol line to usb.ids file?
Date: Tue, 3 Sep 2019 11:43:33 -0400	[thread overview]
Message-ID: <20190903154333.GT4337@nathanst.com> (raw)
In-Reply-To: <20190903133933.GA9435@kroah.com>

On Tue, Sep 03, 2019 at 15:39:33 +0200, Greg KH wrote:
> On Sat, Aug 17, 2019 at 06:01:45PM -0400, Nathan Stratton Treadway wrote:
> > I noticed that when I use "lsusb -v" on a UAS-enabled drive enclosure,
> > the bInterfaceProtocol line for #80/0x50 has a "protocol name" label but the
> > one for #98/0x62 does not:
[...]
> > So...I was wondering if there was any particular reason that protocol
> > 98 isn't included in the usb.ids file?
> 
> No one got around to it?  Feel free to submit a patch to the web site
> that handles these to upate it.

Thanks for your reply.  I did look there first, but because the
"Bulk-Only" and "UAS" protocol names seem so similar but the UAS name
hasn't been created for several years now, I started to wonder if there
was a more complicated background story behind the situation.

Anyway, for what it's worth there was a submission for the UAS protocal
name on the USB ID website in 2013 and I submitted another one a couple
weeks ago, but so far both are still showing up as grey (which seems to
indicate that it's still pending approval by "an admin").
  https://usb-ids.gowdy.us/read/UC/08/06/62

I'll see if I can track down contact information for the admin(s) there.

						Nathan

      reply	other threads:[~2019-09-03 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-17 22:01 Adding "UAS" protocol line to usb.ids file? Nathan Stratton Treadway
2019-09-03 13:39 ` Greg KH
2019-09-03 15:43   ` Nathan Stratton Treadway [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=20190903154333.GT4337@nathanst.com \
    --to=vgerlists@nathanst.com \
    --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 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.