From: Manfred Gruber <m.gruber@tirol.com>
To: linux-hotplug@vger.kernel.org
Subject: usb card reader not detect hotplug of sd/cf cards
Date: Mon, 18 Jun 2007 07:42:44 +0000 [thread overview]
Message-ID: <200706180942.44381.m.gruber@tirol.com> (raw)
hi !
I have problem with a SMSC USB2227/2228 card reader on a embedded device that
it does not detect hotplugging of the cards.
if no sd/cf card is in the slot at booting i get (2.6.22-rc4):
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usb 1-2: new low speed USB device using ep93xx-ohci and address 2
usb 1-2: configuration #1 chosen from 1 choice
usb 1-3: new full speed USB device using ep93xx-ohci and address 3
usb 1-3: configuration #1 chosen from 1 choice
hub 1-3:1.0: USB hub found
hub 1-3:1.0: 4 ports detected
usb 1-3.1: new full speed USB device using ep93xx-ohci and address 4
usb 1-3.1: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
...
scsi 1:0:0:0: Direct-Access Generic Flash HS-CF 4.44 PQ: 0 ANSI: 0
sd 1:0:0:0: Attached scsi removable disk sda
sd 1:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:1: Direct-Access Generic Flash HS-MS 4.44 PQ: 0 ANSI: 0
sd 1:0:0:1: Attached scsi removable disk sdb
sd 1:0:0:1: Attached scsi generic sg1 type 0
scsi 1:0:0:2: Direct-Access Generic Flash HS-SM 4.44 PQ: 0 ANSI: 0
sd 1:0:0:2: Attached scsi removable disk sdc
sd 1:0:0:2: Attached scsi generic sg2 type 0
scsi 1:0:0:3: Direct-Access Generic Flash HS-SD/MMC 4.44 PQ: 0 ANSI: 0
sd 1:0:0:3: Attached scsi removable disk sdd
sd 1:0:0:3: Attached scsi generic sg3 type 0
if I then insert a card i have to do:
echo 1 > /sys/block/sdd/device/rescan
SCSI device sdd: 62720 512-byte hdwr sectors (32 MB)
sdd: Write Protect is off
sdd: assuming drive cache: write through
and then the device is there.
are there on normal linux workstations some daemons running which detect
hotpluging of such devices periodically or how is this handled.
my problem is that on my workstation hotplugging of cards gets detected, but
on the embedded device not.
so dose someone have an idea what to do, or make a small daemon which dose a
echo 1 > /sys/block/sdX/device/rescan periodicall ?
or are there already some daemons which do this job ?
thanks a lot for help
regards
manfred
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2007-06-18 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 7:42 Manfred Gruber [this message]
2007-06-18 12:00 ` usb card reader not detect hotplug of sd/cf cards Kay Sievers
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=200706180942.44381.m.gruber@tirol.com \
--to=m.gruber@tirol.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).