From: "Bob Copeland" <me@bobcopeland.com>
To: Alan Stern <stern@rowland.harvard.edu>,
Bob Copeland <me@bobcopeland.com>,
linux-kernel@vger.kernel.org,
<usb-storage@lists.one-eyed-alien.net>
Cc: phil@ipom.com, Andries.Brouwer@cwi.nl
Subject: Re: [usb-storage] Re: [PATCH] usb-storage: Add support for Rio Karma
Date: Thu, 24 Nov 2005 11:41:30 -0500 [thread overview]
Message-ID: <E1EfKA6-00029s-00@hash.localnet> (raw)
> On Wed, 23 Nov 2005, Bob Copeland wrote:
> > +#ifdef CONFIG_USB_STORAGE_KARMA
> > +UNUSUAL_DEV( 0x045a, 0x5210, 0x0101, 0x0101,
> > + "Rio",
> > + "Rio Karma",
> > + US_SC_SCSI, US_PR_BULK, rio_karma_init, US_FL_FIX_INQUIRY),
>
> Are you sure you need US_SC_SCSI and US_PR_BULK? Wouldn't US_SC_DEVICE
> and US_PR_DEVICE be sufficient?
>
> And do you really need US_FL_FIX_INQUIRY? Hardly any devices do (maybe
> none).
Alan,
Thanks again for your comments.
The Karma does some rather broken things. If you look at the dump below you'll
see that a lot of fields are just zeroed out, such as the serial number. There
are obviously wrong things, e.g. the device class and protocols are zero, but
the interface class is also zero, which is reserved according to the spec. The
protocol is interpreted as CBI but there are actually no control or interrupt
endpoints. Thus US_PR_BULK... and maybe US_SC_SCSI, I'll check that.
I set US_FL_FIX_INQUIRY because I have noticed that, on occasion, the unit
would report itself as being either the USB controller or the disk drive
contained within, so instead of "Rio" it says "HitachiXYZ" or "Cypress," and
the device acts funny. I can only reproduce this rarely on the device, but I
assumed that this flag would help.
T: Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 8 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=045a ProdID=5210 Rev= 1.01
S: Manufacturer=Rio
S: Product=Rio Karma
S: SerialNumber=0000000000000000
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=usb-storage
E: Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I freely admit ignorance on many of the fine points on scsi/usb so please
enlighten me as necessary.
--
Bob Copeland %% www.bobcopeland.com
next reply other threads:[~2005-11-24 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 16:41 Bob Copeland [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-23 11:33 [PATCH] usb-storage: Add support for Rio Karma Bob Copeland
2005-11-23 18:18 ` [usb-storage] " Alan Stern
2005-11-23 18:39 ` Andries Brouwer
2005-11-24 4:08 ` Phil Dibowitz
2005-11-24 11:23 ` Andries Brouwer
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=E1EfKA6-00029s-00@hash.localnet \
--to=me@bobcopeland.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@ipom.com \
--cc=stern@rowland.harvard.edu \
--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