From: David Hinds <dhinds@sonic.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Unloading drivers, start-up, shut-down and a rewrite (a problem)
Date: Fri, 05 Oct 2001 06:25:06 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100226318709917@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100216891319132@msgid-missing>
On Fri, Oct 05, 2001 at 03:58:58PM +1000, Keith Owens wrote:
>
> Before I write the code, what needs to change in user space to match
> the new semantics? Every device activation and inactivation must
> adjust the use count of the supporting module. That is easy for
> hotplug but what about PCMCIA and fixed devices? In particular
> ifconfig eth0 up must adjust the use count of the module controlling
> eth0. A partial solution that only works for hotplug is not a good
> idea. Can we get a consistent user space framework for the new
> semantics?
Just so you know, and not saying whether it is a better or worse
solution, the way PCMCIA drivers handle this, is that there's a
separate interface, /proc/bus/pccard/drivers, that has "use counts"
for PCMCIA drivers that indicate how many physical devices are
currently associated with each driver. These use counts are
independent of the regular module use counts.
-- Dave
_______________________________________________
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
next prev parent reply other threads:[~2001-10-05 6:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 3:14 Unloading drivers, start-up, shut-down and a rewrite (a problem) Stamatis Mitrofanis
2001-10-04 4:29 ` Keith Owens
2001-10-05 0:03 ` Stamatis Mitrofanis
2001-10-05 5:58 ` Keith Owens
2001-10-05 6:25 ` David Hinds [this message]
2001-10-05 7:13 ` David Brownell
2001-10-05 7:21 ` David Brownell
2001-10-05 7:28 ` Keith Owens
2001-10-05 8:16 ` Oliver Neukum
2001-10-05 8:53 ` David Brownell
2001-10-05 15:26 ` David Hinds
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-100226318709917@msgid-missing \
--to=dhinds@sonic.net \
--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).