From: Ed Tomlinson <edt@aei.ca>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Andries E. Brouwer" <Andries.Brouwer@cwi.nl>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: [BUG] 2.6.32 - Sddr-09 SM reader resets endlessly
Date: Sat, 5 Dec 2009 19:00:41 -0500 [thread overview]
Message-ID: <200912051900.41298.edt@aei.ca> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0912051623020.18442-100000@netrider.rowland.org>
On Saturday 05 December 2009 16:34:26 Alan Stern wrote:
> On Sat, 5 Dec 2009, Andries E. Brouwer wrote:
>
> > > Andries, do you have any idea what's going on? Evidently this device
> > > doesn't accept the protocol used by the sddr09 driver.
> >
> > Hi Alan,
> >
> > Sorry, no - I have no memory and worked on these USB drivers
> > years ago. Forgot all details. Also my last sddr09 device broke
> > some time ago.
> >
> > Looking at my old files I do not see the Vendor Id 0781, so maybe
> > this is a device I never encountered.
> > These old files also discuss some trickery with multi-lun devices
> > where the driver needed depends on the lun. This is not a reader
> > of multiple types of card?
> >
> > Many of my SM readers worked with either sddr09 or sddr55.
> > Does the unusual devices section today say that such a device
> > needs sddr09?
> >
> > Found a 2.6.31 source tree. Yes,
> >
> > UNUSUAL_DEV( 0x0781, 0x0200, 0x0000, 0x9999,
> > "Sandisk",
> > "ImageMate SDDR-09",
> > US_SC_SCSI, US_PR_EUSB_SDDR09, usb_stor_sddr09_init,
> > 0),
> >
> > Is it known who added this? Is 0208 in the interval of known devices
> > for which sddr09 works?
>
> The entry was added before 2.5.0 (more than 7 years ago), and I can't
> tell who added it. And the entry doesn't say anything about DPCM
> (multiple-LUN trickery).
>
> Ed, it looks like you're out of luck. Unless you can figure out the
> vendor-specific protocol used by that device, and modify the sddr09
> driver to support it, you won't be able to use the device under Linux.
>
> Or am I completely off base? Did it used to work with an earlier
> kernel? If it did, can you get a usbmon trace of it?
This is a regression. The device works fine in 2.6.31 something
in .32 breaks it.
Ed
next prev parent reply other threads:[~2009-12-06 0:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 23:00 [BUG] 2.6.32 - Sddr-09 SM reader resets endlessly Ed Tomlinson
2009-12-04 15:21 ` Alan Stern
2009-12-05 4:44 ` Ed Tomlinson
2009-12-05 17:55 ` Alan Stern
2009-12-05 20:06 ` Andries E. Brouwer
2009-12-05 21:34 ` Alan Stern
2009-12-06 0:00 ` Ed Tomlinson [this message]
2009-12-06 4:51 ` Alan Stern
2009-12-06 17:07 ` Ed Tomlinson
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=200912051900.41298.edt@aei.ca \
--to=edt@aei.ca \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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