From: Pete Zaitcev <zaitcev@redhat.com>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org, jgarzik@redhat.com
Subject: Re: [usb-storage] drivers/block/ub.c #6
Date: Fri, 27 Aug 2004 20:57:24 -0700 [thread overview]
Message-ID: <20040827205724.64a3c99f@lembas.zaitcev.lan> (raw)
In-Reply-To: <1093645959.8006.219.camel@patlinux.iomegacorp.com>
On 27 Aug 2004 16:32:39 -0600
Pat LaVarre <p.lavarre@ieee.org> wrote:
> Looks to me like we have ub.ko taking over just x 08 06 50, rather than
> all of the x 08 (06|05|02) 50 = bInterfaceClass ...SubClass ...Protocol
> considered generic by MSFT?
>
> http://www.microsoft.com/whdc/device/storage/usbfaq.mspx
> agrees Flash should be x 08 06 50 but gives no clear guidance to the
> rest of us.
>
> I remember we invented x 08 06 50 to be the one tuple to rule them all,
> to move the determination of PDT (peripheral device type) etc. back into
> op x12 "INQUIRY" where it belongs, ...
I'll look at non-bulk once we have something useable by common folks
and Fedora ships ub, but not before. All my devices use Bulk. But also,
UFI has to come first. Only then, perhaps, I'll look at CB and CBI.
> Of course the world may yet contain advocates of connecting HDD/FDD as
> bInterfaceSubClass = x05 "SFF 8070" = Compaq LS-120 or connecting DVD/CD
> as x02 "SFF 8020" = read-only CD.
I don't have any plans for 8070 and 8020i. I promise to look at patches
if someone submits any. However, in my experience, 8070 devices are fickle.
They may be better off left to usb-storage forever, with its richer
infrastructure.
-- Pete
prev parent reply other threads:[~2004-08-28 4:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 10:51 Pete Zaitcev
2004-08-27 21:02 ` [usb-storage] " Pat LaVarre
2004-08-27 22:32 ` Pat LaVarre
2004-08-28 3:57 ` Pete Zaitcev [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=20040827205724.64a3c99f@lembas.zaitcev.lan \
--to=zaitcev@redhat.com \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.lavarre@ieee.org \
--cc=usb-storage@lists.one-eyed-alien.net \
/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
all inboxes | Powered by JetHome®