From: Pat LaVarre <p.lavarre@ieee.org>
To: axboe@suse.de
Cc: mckellj@iomega.com, linux-scsi@vger.kernel.org
Subject: CDC_RAM for lk 2.4, PATCH proposed
Date: 15 Apr 2004 10:52:40 -0600 [thread overview]
Message-ID: <1082047960.15520.82.camel@patibmrh9> (raw)
Jens A:
Would you consider for 2.4.27, a patch written to give us CDC_RAM alone?
I ask because I notice, we don't need the problematic op x46
GPCMD_GET_CONFIGURATION feature x0028 MRW for 2.4.27 to support
CDC_RAM. We only need that for MRW.
Pat LaVarre
P.S.
I speak from a context of you & John M having already done most of the
work:
--- http://sourceforge.net/projects/iomrrdtools/
--- Release Name: writable-patch-0.2
--- http://sourceforge.net/project/shownotes.php?release_id=229527
...
http://w1.894.telia.com/~u89404340/patches/packet/2.4/cd-mrw-2.4.23-rc1.patch.bz2
...
not ... complete MRW [like] lk 2.6.2+
one drive ... respond incorrectly
when doing the GET_CONFIGURATION with 0x28 ...
main reason ... not introduced into lk 2.4.
---
I ask because people connecting the recently announced Iomega RRD drives
have asked me how to mkfs ext in 2.4, to which my answer as yet is
sorry, can't help you, except for people willing to mkfs in /dev/loop
and sg_dd the disc image across.
Also I'm guessing feature fetch per se could be broadly compatible,
because today I grabbed one sample of one of the massively distributed
Microsoft XP SP1 instances beginning USB life:
https://lists.one-eyed-alien.net/pipermail/usb-storage/2004-April/000214.html
The first three commands I see are:
-i x24 -y "12 00:00:00 24 00" // standard "INQUIRY" GPCMD_INQUIRY
-i 8 -y "46 00 00:00:00:00 00 00:08 00" // header alone of GPCMD_GET_CONFIGURATION
-i x80 -y "46 00 00:00:00:00 00 00:80 00" // total available length
...
Soon thereafter my sample proceeds with such familiar &
sufficient-to-discover-rewritable talk as:
-i x20 -y "5A 08 2A:00:00:00 00 00:20 00" // "Capabilities" GPMODE_CAPABILITIES_PAGE
...
-i x0C -y "46 00 00:20:00:00 00 00:0C 00" // "Random Writable" CDF_RWRT
...
-i x0C -y "46 00 00:24:00:00 00 00:0C 00" // "Hardware Defect Management" CDF_HWDM
...
next reply other threads:[~2004-04-15 16:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 16:52 Pat LaVarre [this message]
2004-04-16 12:09 ` CDC_RAM for lk 2.4, PATCH proposed Jens Axboe
2004-04-23 22:25 ` John McKell
2004-04-28 1:46 ` Pat LaVarre
2004-04-28 14:48 ` Pat LaVarre
[not found] ` <1084897080.3746.38.camel@patibmrh9>
2004-05-19 8:15 ` Jens Axboe
2004-05-19 15:45 ` Pat LaVarre
2004-05-20 8:06 ` Jens Axboe
2004-05-20 22:01 ` Pat LaVarre
2004-05-20 23:51 ` Pat LaVarre
2004-05-21 6:53 ` Jens Axboe
2004-05-21 15:28 ` Pat LaVarre
2004-06-03 18:30 ` Pat LaVarre
2004-06-03 18:32 ` Jens Axboe
2004-06-04 14:53 ` Marcelo Tosatti
2004-06-04 15:18 ` Pat LaVarre
2004-06-04 15:24 ` Jens Axboe
2004-06-04 15:27 ` Pat LaVarre
2004-06-04 15:36 ` Jens Axboe
2004-06-18 21:42 ` 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=1082047960.15520.82.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=axboe@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=mckellj@iomega.com \
/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