From: Guest section DW <dwguest@win.tue.nl>
To: andy.piper@freeuk.com
Cc: linux-kernel@vger.kernel.org, aeb@cwi.nl
Subject: Re: Dane-Elec PhotoMate Combo
Date: Sun, 6 May 2001 02:38:13 +0200 [thread overview]
Message-ID: <20010506023813.A5041@win.tue.nl> (raw)
In-Reply-To: <3AF18F40.BD741542@ukgateway.net> <20010503205929.A4187@win.tue.nl> <3AF42A82.C05A2F51@ukgateway.net>
In-Reply-To: <3AF42A82.C05A2F51@ukgateway.net>; from Andy Piper on Sat, May 05, 2001 at 05:29:54PM +0100
On Sat, May 05, 2001 at 05:29:54PM +0100, Andy Piper wrote:
> > For me the Dane-Elec is working and stable.
>
> You are using the Compact Flash reader part of the device, right?
Yes.
> I don't think it is working with SmartMedia.
I cannot test that part - don't think I have any SmartMedia.
> I've tried the latest
> kernel 2.4.5-pre1, which incorporates your patch to allow the device
> to be recognised. The Dane-Elec / SCM eUSB adapter can be seen in
> /proc/bus/usb/devices, but I cannot mount a SmartMedia card (which I'm
> assuming I should be able to mount on /dev/sda; mind you,
Probably sdb.
> /proc/scsi/scsi shows it only as a Compact Flash device, and doesn't
> mention SmartMedia...)
>
> This part looks good:
>
> castor kernel: Vendor: eUSB Model: Compact Flash Rev:
> castor kernel: Type: Direct-Access ANSI SCSI
>
> ... this bit doesn't look good ...
>
> castor kernel: Detected scsi removable disk sda at scsi1, channel 0,
> castor kernel: sda : READ CAPACITY failed.
>
> I've also tried another hack I found in a news posting, advising that
> CONFIG_USB_STORAGE_SDDR09 support should be added to the Config.in for
> /usr/src/linux/drivers/usb and enabled; it hasn't helped.
Yes. If I do that, I see:
<4> Vendor: eUSB Model: Compact Flash Rev:
<4> Type: Direct-Access ANSI SCSI revision: 02
<4> Vendor: SCM Micr Model: eUSB SmartMedia Rev: 0207
<4> Type: Direct-Access ANSI SCSI revision: 02
that is, the enabling of CONFIG_USB_STORAGE_SDDR09 turns this reader
into two devices: a CF reader and a SM reader.
Inserting sd.o yields
Detected scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
Detected scsi removable disk sdc at scsi2, channel 0, id 0, lun 1
that is, the two logical units of this device turn into sdb (the CF reader)
and sdc (the SM reader). The CF reader contains a card, and reading
capacity is successful:
SCSI device sdb: 15872 512-byte hdwr sectors (8 MB)
If one makes the MODE SENSE command read the vendor page 0, it succeeds, and:
sdb: Write Protect is off
There is a single partition on sdb:
sdb1
On the other hand, sdc does not contain anything, so unsurprisingly:
sdc : READ CAPACITY failed.
> Is this a discussion I should take to the usb-devel mailing list?
Probably, yes. You might cc me, I am not subscribed to that list.
Andries - aeb@cwi.nl
next prev parent reply other threads:[~2001-05-06 0:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 17:02 Dane-Elec PhotoMate Combo Andy Piper
2001-05-03 18:59 ` Guest section DW
2001-05-05 16:29 ` Andy Piper
2001-05-06 0:38 ` Guest section DW [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 7:38 Andries.Brouwer
2001-04-29 12:21 Andries.Brouwer
2001-04-30 4:16 ` Matthew Dharm
2001-04-28 15:02 Andries.Brouwer
2001-04-29 1:06 ` Matthew Dharm
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=20010506023813.A5041@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=aeb@cwi.nl \
--cc=andy.piper@freeuk.com \
--cc=linux-kernel@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