From mboxrd@z Thu Jan 1 00:00:00 1970 From: Willem Riede Date: Wed, 16 Feb 2005 23:32:51 +0000 Subject: Re: [ANNOUNCE] hotplug-ng 001 release Message-Id: <1108596771l.5056l.6l@serve.riede.org> List-Id: References: <20050211004033.GA26624@suse.de> In-Reply-To: <20050211004033.GA26624@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On 02/16/2005 06:17:41 PM, Roman Kagan wrote: > On Wed, Feb 16, 2005 at 11:02:41PM +0000, Willem Riede wrote: > > On 02/16/2005 06:07:52 AM, Roman Kagan wrote: > > > It handles only st, sd_mod and sr_mod cases (as > > > hotplug-ng-001/module_scsi.c did). Are there any other? > >=20 > > Not all tapes are supported by st - OnStream drives need osst instead. >=20 > As an excuse I can say that I reproduced what was in > hotplug-ng-001/module_scsi.c, no more, no less :) >=20 > > How do you suggest that is to be handled? >=20 > AFAICS they coexist nicely, so, if you add the same thing to osst.c: >=20 > MODULE_ALIAS("scsi-type-1"); /* TYPE_TAPE */ >=20 > both osst and st will be loaded (provided Greg convinces Rusty to make > modprobe load _all_ matching modules as he suggested the other day). > Then the one whose .probe succeeds will handle the device. >=20 > Will that work? Yes. If we can get that load-all behaviour implemented, everything will be = fine. Thanks, Willem Riede. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=CCk _______________________________________________ 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