From: Pat LaVarre <p.lavarre@ieee.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>,
Alex Sanks <alex@netchip.com>, Julian Back <jback@mpc-data.co.uk>,
David Brownell <david-b@pacbell.net>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: usb storage traces
Date: 04 Dec 2003 14:34:44 -0700 [thread overview]
Message-ID: <1070573684.2269.37.camel@patibmrh9> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0312041509380.994-100000@ida.rowland.org>
> Pat LaVarre says that protocols x02 (SFF-8020i = CD/DVD) and
> x05 (SFF-8070i = Removeable media, floppy) are the most important, since
> they are the only other ones the generic Windows USB mass storage drivers
> recognize.
I mean to be paraphrasing the windows/inf/usbstor.inf quotation:
...
[Generic]
%GenericBulkOnly.DeviceDesc%=USBSTOR_BULK, USB\Class_08&SubClass_02&Prot_50
%GenericBulkOnly.DeviceDesc%=USBSTOR_BULK, USB\Class_08&SubClass_05&Prot_50
%GenericBulkOnly.DeviceDesc%=USBSTOR_BULK, USB\Class_08&SubClass_06&Prot_50
[...
>From that quotation I ignorantly guess that plugging anything other than
x 08 (02|05|06) 50 into Win XP/ 2K/ ME requires an idVendor:idProduct
match (possibly already found elsewhere in Windows e.g. elsewhere in
that same file), else installing a driver (possibly as trivial as
additional .inf text) to match the device.
Pat LaVarre
next prev parent reply other threads:[~2003-12-04 21:55 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 18:30 usb storage traces Alan Stern
2003-12-04 18:44 ` Matthew Dharm
2003-12-04 20:59 ` Alan Stern
2003-12-04 21:27 ` Matthew Dharm
2003-12-04 21:33 ` Pat LaVarre
2003-12-04 21:34 ` Pat LaVarre [this message]
2003-12-04 21:37 ` Pat LaVarre
2003-12-04 21:38 ` Pat LaVarre
2003-12-04 22:24 ` Pat LaVarre
2003-12-04 22:28 ` Pat LaVarre
2003-12-05 3:56 ` Informational Exception mpage [was: usb storage traces] Douglas Gilbert
2003-12-05 15:32 ` Alan Stern
2003-12-05 16:02 ` Pat LaVarre
2003-12-05 15:01 ` usb storage traces Alan Stern
2003-12-05 17:18 ` bCWBCBLength is cb length no when Pat LaVarre
2003-12-05 18:55 ` Alan Stern
2003-12-05 19:29 ` Pat LaVarre
2003-12-05 17:19 ` usb storage traces Pat LaVarre
2003-12-05 18:22 ` Alan Stern
2003-12-05 5:08 ` Patrick Mansfield
2003-12-05 16:01 ` Alan Stern
2003-12-05 16:11 ` Pat LaVarre
2003-12-05 17:14 ` David Brownell
2003-12-05 17:35 ` Pat LaVarre
2003-12-05 18:21 ` Alan Stern
2003-12-05 18:41 ` Pat LaVarre
2003-12-05 18:24 ` David Brownell
2003-12-16 17:00 ` Randy.Dunlap
2003-12-16 17:07 ` Pat LaVarre
2003-12-05 4:31 ` Douglas Gilbert
[not found] <20031219091450.GC828@one-eyed-alien.net>
2003-12-19 14:51 ` Alan Stern
2003-12-19 16:21 ` Pat LaVarre
2003-12-20 23:56 ` Matthew Dharm
2003-12-21 2:26 ` Alan Stern
[not found] <1070649445.12411.347.camel@patibmrh9>
2003-12-05 19:27 ` Alan Stern
2003-12-05 20:27 ` Pat LaVarre
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 16:13 Pat LaVarre
2003-11-10 22:04 Pat LaVarre
2003-11-11 21:59 ` Pat LaVarre
2003-11-13 18:42 ` Pat LaVarre
2003-09-22 23:07 [linux-usb-devel] Re: USB storage problems on OHCI Andries.Brouwer
2003-09-22 23:25 ` usb storage traces Pat LaVarre
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=1070573684.2269.37.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=alex@netchip.com \
--cc=david-b@pacbell.net \
--cc=jback@mpc-data.co.uk \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=stern@rowland.harvard.edu \
/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