From: David Hinds <dhinds@sonic.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: definition of terms (was: Re: Adding PCMCIA support to the kernel tree -- developers needed.)
Date: Fri, 09 Feb 2001 17:30:31 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98174042208350@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98173830701779@msgid-missing>
I think this discussion is trying to create a very difficult problem
out of something that really is not that hard to handle in practice.
Say you insert one hot plug device then in the next microsecond swap
it out and swap in another device of the same type but that you want
to configure differently. Is this really a scenario that deserves
serious discussion? I would simply require serialization of hot plug
agent actions and then it seems to me that 90% of the theoretical
problem (and 99.999% of the real problem) goes away. If you try to
redesign the entire Linux device model to handle a hot plug corner
case, you're wasting your time because your changes will never be
accepted; DevFS is a minor change in comparison.
PCMCIA does handle these issues and the solution (serializing device
configuration actions, and configuring devices based on physical
location and/or device properties rather than device names) works.
-- Dave
_______________________________________________
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-02-09 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 17:03 definition of terms (was: Re: Adding PCMCIA support to the kernel tree -- developers needed.) Oliver Neukum
2001-02-09 17:30 ` David Hinds [this message]
2001-02-09 18:53 ` Vojtech Pavlik
2001-02-10 10:30 ` Oliver Neukum
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-98174042208350@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).