From: Brad Hards <bhards@bigpond.net.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: (remove) event not supported.
Date: Sat, 31 Mar 2001 01:00:26 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98600042525039@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98597321622555@msgid-missing>
David Brownell wrote:
>
> > Mar 30 08:07:01 localhost /etc/hotplug/usb.agent: USB remove event not supported
> >
> > What are the issues associated with it. Is this something that just
> > hasn't been coded up or is it something that can't be coded up.
>
> Awkward to code up. What one really wants to happen is have
> the device's module removed ... and _maybe_ some driver-specific
> action (not that I can think of any examples just now). But:
umounting a storage device? Or does that happen automatically? I am
not going to pull out a mounted zip drive to find out...
> - the dynamic linking framework doesn't track how many devices
> are attached to each driver module ... so if there's another device
> controlled by the same driver, but it's not opened, removing that
> module would be incorrect. ("module use count" doesn't cover
> uses, just opens.)
This could be trivially extended to have a inc_dev_open_count() and
inc_dev_use_count(), where the use count get incremented in probe()
and the open count gets incremented in open(). Naturally you also
have to have a dec version of each as well, in disconnect() and
close().
> - nothing's tracking which modules are used with which device,
> and if the device is gone you can't query it to find that out!
maybe the driver could have a list of devices? not so easy to
implement though.
Brad
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-03-31 1:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 17:21 (remove) event not supported David Brownell
2001-03-31 1:00 ` Brad Hards [this message]
2001-03-31 2:03 ` Keith Owens
2001-03-31 2:12 ` Brad Hards
2001-03-31 3:48 ` David Hinds
2001-03-31 8:55 ` Brad Hards
2001-03-31 14:56 ` David Brownell
2001-03-31 15:02 ` David Brownell
2001-03-31 15:49 ` Keith Owens
2001-03-31 16:05 ` David Brownell
2001-03-31 16:18 ` Keith Owens
2001-03-31 16:52 ` David Brownell
2001-04-01 3:02 ` David Hinds
2001-04-01 3:03 ` David Hinds
2001-04-01 5:26 ` Douglas Gilbert
2001-04-02 2:56 ` Trond Eivind Glomsrød
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=marc-linux-hotplug-98600042525039@msgid-missing \
--to=bhards@bigpond.net.au \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).