[7664] in linux-scsi channel archive
How do I invoke a re-probe from kernel space?
daemon@ATHENA.MIT.EDU (Matthew Dharm)
Sun Dec 12 01:35:42 1999
Date: Sat, 11 Dec 1999 22:34:21 -0800 (PST)
From: Matthew Dharm <mdharm@one-eyed-alien.net>
Reply-To: Matthew Dharm <mdharm@one-eyed-alien.net>
To: linux-scsi@vger.rutgers.edu
Message-ID: <Pine.LNX.4.10.9912112229590.27606-100000@ziggy.one-eyed-alien.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi, all. Let me start by asking that any replies to this be CC'ed to me,
as I'm not on the linux-scsi mailing list.
I'm working on the USB Mass Storage driver, which appears to be a SCSI
host controller to the kernel. The question I have is this: how do I
inform the higher SCSI layers that a device has appeared and disappeared?
Mostly, I'm concerned with when devices appear. I can trace the code flow
when a user does an "echo 'scsi add-single-device 0 0 0 0' >
/proc/scsi/scsi, but is that safe to call at all times? Are there any
restrictions on it's use?
As for removal, I'm creating a false sense of persistance in this virtual
host driver to allow people to remove and reattach devices, so the SCSI
higher layer never notices that the device is gone. However, I might want
the driver to 'forget' about a device, and thus I need a way to ask the
SCSI layer to do the equivalent of a "echo 'scsi remove-single-device'..."
also. Again, I can trace the code flow, but is it safe at all times?
What are the warnings/caveats that come with these functions?
Matt Dharm
--
Matthew Dharm InterNIC: MDD94
Engineer, Qualcomm, Inc. Cell: (619) 890-6943
Home: mdharm@one-eyed-alien.net Home: (858) 689-1908
Work: mdharm@qualcomm.com Work: (858) 651-7649
Beep: page-matt@one-eyed-alien.net Beep: (858) 621-8155
E: You run this ship with Windows?! YOU IDIOT!
L: Give me a break, it came bundled with the computer!
-- ESR and Lan Solaris
User Friendly, 12/8/1998
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
