From: Roman Kagan <rkagan@mail.ru>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Willem Riede <osst@riede.org>,
linux-scsi@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] hotplug-ng 001 release
Date: Fri, 18 Feb 2005 22:41:35 +0300 [thread overview]
Message-ID: <20050218194135.GD4424@katya> (raw)
In-Reply-To: <20050218183350.GA21954@us.ibm.com>
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.
next prev parent reply other threads:[~2005-02-18 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050211193627.GB20015@suse.de>
[not found] ` <20050211204626.GC2568@katya>
[not found] ` <20050211211028.GB21512@suse.de>
[not found] ` <20050212003458.GI2568@katya>
[not found] ` <20050214224208.GC13110@suse.de>
[not found] ` <20050216105117.GB2360@katya>
[not found] ` <20050216110752.GC2360@katya>
[not found] ` <1108594961l.5056l.5l@serve.riede.org>
[not found] ` <20050216231741.GD2870@katya>
[not found] ` <1108596771l.5056l.6l@serve.riede.org>
2005-02-18 17:17 ` [ANNOUNCE] hotplug-ng 001 release Patrick Mansfield
2005-02-18 18:11 ` Roman Kagan
2005-02-18 18:33 ` Patrick Mansfield
2005-02-18 19:41 ` Roman Kagan [this message]
2005-02-18 20:17 ` Patrick Mansfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050218194135.GD4424@katya \
--to=rkagan@mail.ru \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=osst@riede.org \
--cc=patmans@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox