From: "Razza" <rjames31@btopenworld.com>
To: linux-hotplug@vger.kernel.org
Subject: udev problem DVB-S/T Cards
Date: Sat, 28 Apr 2007 10:49:12 +0000 [thread overview]
Message-ID: <000301c78982$db8615e0$929241a0$@com> (raw)
All,
I have been playing with udev as I need to pin specific identical DVB cards
to specific nodes, mixing DVB-S and DVB-T is bad!
I have found how to identify cards etc. but getting the rule right is
confusing me. I am running Fedora Core 5 and have the following standard
rule in "/etc/udev/rules.d/50-udev.rules" -
SUBSYSTEM="dvb", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf
dvb/adapter%%i/%%s $${K%%%%.*} $${K#*.}'", NAME="%c", MODE="0660"
The closest I got to getting things working was by substituting
"dvb/adapter%%i/" with "dvb/adapter5/", thus forcing the adapter to
/dev/dvb/adapter5, rule below -
BUS="pci", ID="0000:01:06.0", SYSFS{device}="0x7146",
SYSFS{vendor}="0x1131", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf
dvb/adapter5/%%s $${K%%%%.*} $${K#*.}'", NAME="%c", MODE="0660"
Unfortunately that changed the tree/node structure from the norm -
/dev/dvb/
`-- adapter5
|-- ca0
|-- demux0
|-- dvr0
|-- frontend0
`-- net0
To -
/dev/dvb/
`-- adapter5
|-- 0dvb
| `-- adapter5
| |-- ca0
| |-- demux0
| |-- dvr0
| |-- frontend0
| `-- net0
`-- event3dvb
`-- adapter5
`-- event3
I think the problem I am having is that the original rule is based on the
top section of my "udevinfo -a -p $(udevinfo -q path -n
/dev/dvb/adapter0/frontend0)" response, my rule is based on the second
section, thus introducing additional layers as it's further down the
hardware/kernel stack?
My "udevinfo -a -p $(udevinfo -q path -n /dev/dvb/adapter0/frontend0)"
response is as follows -
looking at device '/class/dvb/dvb0.frontend0':
KERNEL="dvb0.frontend0"
SUBSYSTEM="dvb"
SYSFS{dev}="212:3"
looking at device '/devices/pci0000:00/0000:00:10.0/0000:01:06.0':
ID="0000:01:06.0"
BUS="pci"
DRIVER="budget_ci dvb"
SYSFS{msi_bus}=""
SYSFS{broken_parity_status}="0"
SYSFS{enable}="1"
SYSFS{modalias}="pci:v00001131d00007146sv000013C2sd00001017bc04sc80i00"
SYSFS{local_cpus}="1"
SYSFS{irq}="18"
SYSFS{class}="0x048000"
SYSFS{subsystem_device}="0x1017"
SYSFS{subsystem_vendor}="0x13c2"
SYSFS{device}="0x7146"
SYSFS{vendor}="0x1131"
looking at device '/devices/pci0000:00/0000:00:10.0':
ID="0000:00:10.0"
BUS="pci"
DRIVER=""
SYSFS{msi_bus}="1"
SYSFS{broken_parity_status}="0"
SYSFS{enable}="1"
SYSFS{modalias}="pci:v000010DEd0000026Fsv00000000sd00000000bc06sc04i01"
SYSFS{local_cpus}="1"
SYSFS{irq}="0"
SYSFS{class}="0x060401"
SYSFS{subsystem_device}="0x0000"
SYSFS{subsystem_vendor}="0x0000"
SYSFS{device}="0x026f"
SYSFS{vendor}="0x10de"
Can anyone advise of the correct rule?
Thanks in advance!
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2007-04-28 10:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 10:49 Razza [this message]
2007-05-02 8:47 ` udev problem DVB-S/T Cards Razza
2007-05-02 11:08 ` Bryan Kadzban
2007-05-02 12:10 ` Razza
2007-05-02 12:36 ` Matthias Schwarzott
2007-05-02 13:31 ` Matthias Schwarzott
2007-05-02 21:38 ` Razza
2007-05-02 22:20 ` Bryan Kadzban
2007-05-02 23:48 ` Razza
2007-05-03 1:56 ` Bryan Kadzban
2007-05-03 9:10 ` Razza
2007-05-03 11:12 ` Bryan Kadzban
2007-05-03 11:54 ` Razza
2007-05-03 12:13 ` Matthias Schwarzott
2007-05-07 17:18 ` Razza
2007-05-09 17:49 ` Razza
2007-05-30 10:35 ` Razza
2007-07-12 9:05 ` Razza
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='000301c78982$db8615e0$929241a0$@com' \
--to=rjames31@btopenworld.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.