netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: David Woodhouse <dwmw2@infradead.org>
Cc: Harald Hoyer <harald@redhat.com>,
	linux-hotplug@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: udev can't name PS3's network devices correctly
Date: Mon, 14 Apr 2008 14:51:00 +0200	[thread overview]
Message-ID: <20080414125100.GA13564@bongo.bofh.it> (raw)
In-Reply-To: <1208167737.31695.32.camel@pmac.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

On Apr 14, David Woodhouse <dwmw2@infradead.org> wrote:

> Actually it's a generic problem. It also occurs on OLPC, where the
> libertas wireless device presents two interfaces with the same MAC
And on some Sun systems as well.

> > Unconditionally adding a KERNEL key means that persistent names will
> > break if a driver changes the base name (e.g. wlan* -> eth*).
> Drivers shouldn't do that. It'll change the name of the device and may
But they do...

> We could modify the libertas and gelic (and any other affected) drivers
> to provide a dev_id, make sure it's exported in sysfs, and then use that
> in the udev rules. Would that make you happy?
Yes, I like not fixing just the symptoms. :-)

> It has implications w.r.t. the autoconfigured IPv6 addresses of those
> devices,
How so?

> > This workaround should be confined to the PS3 install media, there is
> > no reason to add it to general-purpose distributions.
> Our general-purpose distribution installs and runs on PS3. :)
So if PS3 needs special hacks they should be special-cased to only by
used on PS3 hardware.

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-04-14 12:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ftdb3v$tls$1@ger.gmane.org>
     [not found] ` <20080407143805.GA9492@bongo.bofh.it>
2008-04-14 10:08   ` udev can't name PS3's network devices correctly David Woodhouse
2008-04-14 11:11     ` David Woodhouse
2008-04-14 11:55       ` Kay Sievers
2008-04-14 12:32         ` [PATCH] Expose netdevice dev_id through sysfs David Woodhouse
2008-04-20  1:33           ` David Miller
2008-04-20  5:21             ` Andrey Borzenkov
2008-04-20  5:32               ` David Miller
2008-04-20 10:50             ` David Woodhouse
2008-04-20 10:55               ` David Miller
2008-04-20 11:12                 ` David Woodhouse
2008-04-20 11:14                   ` David Miller
2008-04-20 11:22         ` David Woodhouse
2008-04-27 17:37         ` udev can't name PS3's network devices correctly David Woodhouse
2008-04-27 18:28           ` Kay Sievers
2008-04-14 12:03     ` Kay Sievers
2008-04-14 12:19       ` David Woodhouse
2008-04-14 12:52         ` Kay Sievers
2008-04-14 13:16           ` David Woodhouse
2008-04-14 12:51     ` Marco d'Itri [this message]
2008-04-14 13:38       ` David Woodhouse

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=20080414125100.GA13564@bongo.bofh.it \
    --to=md@linux.it \
    --cc=dwmw2@infradead.org \
    --cc=harald@redhat.com \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=netdev@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).