[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B2A4CD1.1070004@draisberghof.de>
Date: Thu, 17 Dec 2009 16:22:57 +0100
From: Josua Dietze <digidietze@...isberghof.de>
To: Oliver Neukum <oliver@...kum.org>
CC: Matthew Dharm <mdharm-kernel@...-eyed-alien.net>,
Dan Williams <dcbw@...hat.com>,
Stefan Seyfried <stefan.seyfried@...glemail.com>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
usb-storage@...ts.one-eyed-alien.net,
Stefan Seyfried <seife@...airon.com>
Subject: Re: [PATCH] move eject code from zd1211rw to usb-storage
Oliver Neukum schrieb:
> Am Donnerstag, 17. Dezember 2009 14:33:06 schrieb Josua Dietze:
>> If you are thinking about the two specific devices at hand
>> there is no need to tell them apart. Same IDs on plugin, same
>> switching procedure, different IDs on return, different drivers
>> take care.
>
> How do you issue an eject command without a /dev/sgX node?
You're thinking of handling one device in the kernel and the other
one (same ID, same switching procedure) on the outside?
Well, as I said, you'd have to "filter" additional data (USB
model/manufacturer etc., SCSI_INQUIRY strings). But obviously you
would need to have the data of the two devices to note the differences.
BTW, usb_modeswitch does not need SCSI device nodes, because it
talks to the USB device directly via the bulk message layer once the
endpoints are up. Slight advantage over "eject".
Cheers,
Josua
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists