From: Greg KH <greg@kroah.com>
To: "Robert Love" <rml@tech9.net>, "Andrew Morton" <akpm@zip.com.au>,
"christophe barbé" <christophe.barbe.ml@online.fr>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 3c59x and resume
Date: Sun, 24 Mar 2002 00:07:29 -0800 [thread overview]
Message-ID: <20020324080729.GD16785@kroah.com> (raw)
In-Reply-To: <20020323161647.GA11471@ufies.org> <3C9CCBEB.D39465A6@zip.com.au> <1016914030.949.20.camel@phantasy> <20020323224433.GB11471@ufies.org>
On Sat, Mar 23, 2002 at 05:44:33PM -0500, christophe barbé wrote:
> With the 'everything is module' and 'everything is hotplug' approach in
> mind (which is a appealing way and IMHO this is the way we are going),
> I see two part for this problem:
>
> . Persistence after plug out/plug in
>
> . Persistence after suspend/resume
>
> The first one is a userland problem. The card identification could be
> based on the MAC address (for NICs at least, in the case of cardbus the
> bus position has no real signification). This should then be the
> responsibility of the userspace tool (hotplug) to indicate the correct
> option for this card. The problem is when the module is already loaded,
> the userspace tool has no way to indicate this option.
Untrue. See
http://www.kroah.com/linux/hotplug/ols_2001_hotplug_talk/html/mgp00014.html
for a 6 line version of /sbin/hotplug that always assigns the same
"ethX" value to the same MAC address. I think the patch to nameif has
gone in to support this, but I'm not sure.
And why is there a limitation of only 8 devices? Why not do what all
USB drivers do, and just create the structure that you need to use at
probe() time, and destroy it at remove() time?
Just my $0.02
thanks,
greg k-h
next prev parent reply other threads:[~2002-03-24 8:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-23 16:16 [PATCH] 3c59x and resume christophe barbé
2002-03-23 18:39 ` Andrew Morton
2002-03-23 20:06 ` Robert Love
2002-03-23 22:44 ` christophe barbé
2002-03-24 8:07 ` Greg KH [this message]
2002-03-24 14:25 ` christophe barbé
2002-03-25 18:01 ` Greg KH
2002-03-25 18:19 ` christophe barbé
2002-03-25 19:11 ` Greg KH
2002-03-25 20:27 ` christophe barbé
2002-03-25 20:58 ` christophe barbé
2002-03-25 11:34 ` Joachim Breuer
2002-03-25 11:53 ` Xavier Bestel
2002-03-25 21:31 ` Joachim Breuer
2002-03-25 19:44 ` Bill Davidsen
2002-03-25 20:16 ` christophe barbé
2002-03-26 0:57 ` Jeff Garzik
2002-03-26 1:40 ` christophe barbé
2002-03-26 4:10 ` Jeff Garzik
2002-03-26 4:39 ` christophe barbé
2002-03-26 4:50 ` Andrew Morton
2002-03-26 16:56 ` christophe barbé
2002-03-26 16:57 ` Jeff Garzik
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=20020324080729.GD16785@kroah.com \
--to=greg@kroah.com \
--cc=akpm@zip.com.au \
--cc=christophe.barbe.ml@online.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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