From: Erik Andersen <andersen@codepoet.org>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andre Hedrick <andre@linux-ide.org>
Subject: Re: [RFC] /proc/ide/hdx/settings with ide-default pseudo-driver is a 2.6/2.7 show-stopper
Date: Thu, 28 Aug 2003 19:19:10 -0600 [thread overview]
Message-ID: <20030829011910.GA19351@codepoet.org> (raw)
In-Reply-To: <200308281747.11359.bzolnier@elka.pw.edu.pl>
On Thu Aug 28, 2003 at 05:47:11PM +0200, Bartlomiej Zolnierkiewicz wrote:
> Problem is when integrating ide with driverfs.
> Then you need to register/unregister ide-default as driverfs driver
> and now it can "steal" devices, ie. you have cd drive owned by ide-default,
> later you load ide-cdrom driver and your cd drive needs to be unregistered
> from ide-default driver first before it can be registered with ide-cdrom
> driver - you need to add code to do this or device will be "stealed".
> Its not very hard to do but it adds complexity.
Make an interface whereby ide-cdrom (and ide-disk, etc) can walk
the list of all unclaimed devices (i.e. devices owned by
ide-default), check they are of the correct type, and claim them
(thereby removing them from the ide-default driver). When
unregistering, reverse the process and give the device back to
ide-default... i.e. make ide-default a holding pen for unclaimed
devices,
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2003-08-29 1:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 14:46 Bartlomiej Zolnierkiewicz
2003-08-28 15:13 ` Alan Cox
2003-08-28 15:47 ` Bartlomiej Zolnierkiewicz
2003-08-28 18:06 ` Alan Cox
2003-08-28 18:39 ` Bartlomiej Zolnierkiewicz
2003-08-28 19:42 ` Alan Cox
2003-08-29 1:19 ` Erik Andersen [this message]
2003-08-29 9:51 ` Alan Cox
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=20030829011910.GA19351@codepoet.org \
--to=andersen@codepoet.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®