From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roman Kagan Date: Fri, 18 Feb 2005 19:41:35 +0000 Subject: Re: [ANNOUNCE] hotplug-ng 001 release Message-Id: <20050218194135.GD4424@katya> List-Id: References: <20050212003458.GI2568@katya> <20050214224208.GC13110@suse.de> <20050216105117.GB2360@katya> <20050216110752.GC2360@katya> <1108594961l.5056l.5l@serve.riede.org> <20050216231741.GD2870@katya> <1108596771l.5056l.6l@serve.riede.org> <20050218171737.GA20012@us.ibm.com> <20050218181106.GC4424@katya> <20050218183350.GA21954@us.ibm.com> In-Reply-To: <20050218183350.GA21954@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Patrick Mansfield Cc: Willem Riede , linux-scsi@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net On Fri, Feb 18, 2005 at 10:33:50AM -0800, Patrick Mansfield wrote: > The block SG_IO handles the ioctls, but not devices without a SCSI upper > level driver (i.e. not tape, disk or cdrom). Then it might make sense to explicitly list in sg.c the TYPE_* not matched by s[dtr]. > In my experience, there are always applications that want to use the > standard device driver (/dev/sda etc.) and others that want to use a > generic driver. So these drivers can compete for the same device? Are there deterministic rules on which one is supposed to win? And is there a userspace interface to unbind one driver and bind another? Otherwise it may mean that automatic module loading is inappropriate here at all... Roman. ------------------------------------------------------- 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_id396&op=click _______________________________________________ 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