public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Taylor <dan.taylor2@ca.rr.com>
To: linux-media@vger.kernel.org
Subject: Re: Order of dvb devices
Date: Sat, 16 Jan 2010 00:36:37 -0800	[thread overview]
Message-ID: <4B517A95.9090908@ca.rr.com> (raw)


Mika Laitio wrote:
>> True, the ordering is not exactly the same everytime. One will need to
>> provide PCI Bus related info also to a practical udev configuration to
>> get things sorted out in a sane way, rather than anything else.
>
> At least in Mandriva, the order and naming of network adapters are handled by using a this kind of udev rule which prevents for example eth0 and eth1 to swap between boots:
>
> [lamikr@iiris rules.d]$ cat 70-persistent-net.rules
> # This file was automatically generated by the /lib/udev/write_net_rules
> # program, run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single
> # line, and change only the value of the NAME= key.
>
> # Drakx-net rule for eth0 (00:24:e8:9e:66:13)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:11:22:33:44:55", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0
>
> # PCI device 0x8086:0x4232 (iwlagn)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="11:22:33:44:55:66", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0""
>
> I am not sure whether udev rules itself can originally generate this file or whether it's mandriva's own tools/scripts that will generate this file and add all new adapters it finds that are not yet in the file.
>
> Mika


The eth drivers have one advantage:  nearly all of them have an
associated MAC address, which is (supposed to be, anyway) globally
(the planet, not just the system) unique.  It is, therefore, easy
enough to associate a specific NIC with a specific name, as shown.

If we keep some sort of configuration table:

For those boards that have eeproms, and for which the eeprom contains
a serial number, or other unique identifier, we could do the same thing.

Alternatively, we could use the PCI address (bus/device/unit).

USB devices can have serial numbers, but it isn't common.

Sounds like we need to think about keeping a table, having some udev
rules to work with it, and some utility to manage it.

RFQ time?

> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

             reply	other threads:[~2010-01-16  8:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16  8:36 Dan Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-14 15:35 Order of dvb devices Andreas Besse
2010-01-14 15:46 ` Devin Heitmueller
2010-01-14 16:01   ` Andreas Besse
2010-01-14 16:09     ` Devin Heitmueller
2010-01-14 17:19       ` Michael Krufky
2010-01-15 23:00       ` Oliver Endriss
2010-01-15 23:05         ` Devin Heitmueller
2010-01-15 23:08         ` Manu Abraham
2010-01-16  6:50           ` Mika Laitio
2010-01-18  8:58           ` Andreas Besse
2010-01-18 10:32             ` Manu Abraham
2010-01-18 13:16               ` Andreas Besse
2010-01-15 23:12         ` hermann pitton

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=4B517A95.9090908@ca.rr.com \
    --to=dan.taylor2@ca.rr.com \
    --cc=danieltaylor@acm.org \
    --cc=linux-media@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