From: Pat LaVarre <p.lavarre@ieee.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Douglas Gilbert <dougg@torque.net>,
linux-scsi@vger.kernel.org,
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>
Subject: Re: Informational Exception mpage [was: usb storage traces]
Date: 05 Dec 2003 09:02:25 -0700 [thread overview]
Message-ID: <1070640144.12411.18.camel@patibmrh9> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0312051025560.850-100000@ida.rowland.org>
> According to the USB Mass Storage Class - UFI Command Specification, which
> might be more applicable in this circumstance,
Please NO!!!!!!!!!!
On this digressing point, I think all the applicable English texts
actually agree with each other and with reality.
UFI applies exclusively to usb-storage devices with the corresponding
bInterfaceSubClass. I think I remember that is x04, not found in Win
generic x 08 (02|05|06) 50.
Personally I haven't yet had to grok UFI. I could choose instead to
study only ANSI T10 SCSI and SFF SCSI and USB Bootable SCSI. Each of
those have dozens of subflavours. I don't want to have to start
studying a fourth major flavour as yet confined only to USB1FS CBI/CB
FDD, though rumoured to be coming to USB2HS BBB.
Pat LaVarre
next prev parent reply other threads:[~2003-12-05 16:02 UTC|newest]
Thread overview: 30+ 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
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 [this message]
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
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=1070640144.12411.18.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=alex@netchip.com \
--cc=david-b@pacbell.net \
--cc=dougg@torque.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