linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Order of DVB devices
Date: Tue, 26 Jan 2010 15:22:29 +0000	[thread overview]
Message-ID: <20100126152229.GA3113@kroah.com> (raw)
In-Reply-To: <4B5EFDF7.8090709@motama.com>

On Tue, Jan 26, 2010 at 03:36:39PM +0100, Andreas Besse wrote:
> Hello,
> 
> i have a system with multiple DVB cards of the same type and want to
> specify the order of the devices /dev/dvb/adapterX. The device plugged
> into the physical PCI slot 1 on the mainboard should be assigned to
> /dev/dvb/adapter0 and the card in PCI slot 2 should be assigned to
> /dev/dvb/adapter1.
> 
> To identify a DVB card I looked at the output of udevinfo for 2 DVB
> devices. The devices don't provide a serial, so the difference is only
> in the KERNELS parameter (e.g. KERNELS="0000:02:00.0" vs.
> KERNELS="0000:03:00.0"). The Kernels parameter seem to reflect the PCI
> Bus ID.
> 
> According to the thread
> http://thread.gmane.org/gmane.linux.kernel.pci/7446/focust47 on the
> linux-pci mailinglist, the PCI Bus ID is *not* deterministic and
> totally random determined at boot. 
> 
> In the following post
> http://thread.gmane.org/gmane.linux.kernel.pci/7446/focust67 there
> is mentioned that the order of the devices can be specified by using
> udev rules.
> 
> But how this can be done? Which information in /sys can be used to
> determine which DVB device is connected to which specific slot?

Did you try the latest version of udev that has the persistant rules for
the v4l devices in it and look at the symlinks that are created to see
if they solve the problem for you?

thanks,

greg k-h

  reply	other threads:[~2010-01-26 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 14:36 Order of DVB devices Andreas Besse
2010-01-26 15:22 ` Greg KH [this message]
2010-01-27  4:18 ` Kay Sievers
2010-01-27 13:38 ` Andreas Besse

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=20100126152229.GA3113@kroah.com \
    --to=greg@kroah.com \
    --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).