From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] CDC_WR
Date: 11 Nov 2003 15:24:00 -0700 [thread overview]
Message-ID: <1068589440.5909.33.camel@patrh9> (raw)
In-Reply-To: <1068485442.4495.25.camel@patrh9>
> Slanderous or not, also I hear:
6) We may have good precedent for our idea of (a) fetch header, (b)
interpret additional length, then (c) fetch all available op x46 Get
Configuration data.
Specifically we have one sample of Windows XP SP1 starting life after
plug in with that politically correct speech:
http://marc.theaimsgroup.com/?l=linux-scsi&m=106858800007411
List: linux-scsi
Subject: Re: usb storage traces
Date: 2003-11-11 21:59:22
7) Fetching all the device configuration this way lets us see the
"profile list". Testing whetrher the profile list contains one or more
writable profiles, none of which are DVD+RW, might be our best mmc way
of guessing if open of device should fail via EROFS or no.
Pat LaVarre
next prev parent reply other threads:[~2003-11-11 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 15:58 [PATCH] CDC_WR Pat LaVarre
2003-11-10 17:30 ` Pat LaVarre
2003-11-11 22:24 ` Pat LaVarre [this message]
2003-11-13 22:35 ` Pat LaVarre
2003-11-13 22:47 ` Pat LaVarre
2003-11-14 18:10 ` 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=1068589440.5909.33.camel@patrh9 \
--to=p.lavarre@ieee.org \
--cc=linux-scsi@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