Please, please include the [EMAIL PROTECTED]
list in your discussions of hotplug related issues.  If you are
personally involved in hotplug related development, please also
join the list.  Getting hotplug sorted out right is going to probably
be a major focus throughout the 2.5 development cycle and I expect the
results will be far better if we all learn from each other and
contribute to refining the core and shared functionality.

You can sign up here:

   http://lists.sourceforge.net/mailman/listinfo/linux-hotplug-devel

Many thanks,

        Miles


James Goodwin wrote:

>>>> scsi_add_device         | Add an identified device to the system.
>>> 
>>> Yes, similar functionality to:
>>> echo "scsi add-single-device <h> <b> <t> <l>" > /dev/scsi/scsi
>>> 
>>> so how about a scsi_remove_device() for the complementary
>>> "remove-single-device" functionality. Could be useful when
>>> hot unplugging.
>>> 
>> 
>> Sounds reasonable.
>> Actually scsi_add_device just adds this Scsi_Device_Template to the
>> global scsi_devicelist. It may just as well be part of
>> scsi_register_upper. scsi_add_device/scsi_remove_device could then be
>> the complementary to using proc for adding devices as you suggests.
> 
> 
> Something like scsi_add_device/scsi_remove_device as described above would
> be "very" helpful for the IEEE-1394 SBP-2 hot-plugging support. The "add"
> part is quite simple, since it ultimately just calls scan_scsis. The
> "remove" part is a bit more difficult, unless the user has unmounted the
> disk before hot-unplugging it, because of the attached usage count. Douglas
> has mentioned that the usage count could be made more accurate to help with
> this...   ;-)
> 
> Cheers,
> --James
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to [EMAIL PROTECTED]


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]

Reply via email to