From: "Razza" <rjames31@btopenworld.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: udev problem DVB-S/T Cards
Date: Thu, 03 May 2007 09:10:19 +0000 [thread overview]
Message-ID: <000a01c78d62$dffcb320$9ff61960$@com> (raw)
In-Reply-To: <000301c78982$db8615e0$929241a0$@com>
Bryan Kadzban wrote on 03 May 2007 02:56:
-------------8< Snip! >8-------------
> Just that you (probably unintentionally) ignored one thing that
> Matthias said[1] -- the path_id script doesn't have support for DVB
> devices (at this point). It needs to have support added before this
> set of rules will work correctly.
TBH, I did pick up on Matthias' statement about path-id, in fact I mailed
him back to say i'll wait till he finds the other bits (path-id) as I can do
without breaking anything else on my machine.
Note to self: Do not use force options on an array after you have loaded all
your media!
I then re-read the message and thought maybe he simply meant the following
statement needed adding for each device: ENV{ID_PATH}="pci-0000:00:0b.0-",
ENV{ID_DVB_ADAPTER}="0" , which I duly did.
-------------8< Snip! >8-------------
> To fix the problem, you'd have to add DVB support to /lib/udev/path_id
> -- but I don't know what the devpath looks like for DVB devices, so I
> don't know how you'd do that for sure. I suspect you only have to add
> a "dvb" entry to the case statement near the bottom of the file (make
> it look just like the others), because once that's recognized, it
> *should* use the already-present PCI-bus code. But I can't test that
> myself.
I can now see where you are coming from as: IMPORT{program}="path_id %p" is
calling the path_id script.
I have located path_id which is in /sbin on Fedora core 5, there are some
pretty long case statements in there (one I counted had 47 lines!), the
simplest and last I could find is -
case "$TYPE" in
block)
handle_block
;;
*)
RESULT=1
;;
esac
I have been trying to walk through some sections of this file for the last
couple of hours and have to admit, I am totally out of my depth. I'm not
even sure if I have the right path_id file, the commented section at the top
of path_id states "provide the shortest possible unique hardware path to a
block device for the udev persistent disk device naming scheme" - clearly
i'm not playing with block devices.
Can anyone provide the necessary case section I need, or is there any info I
can give which would help? Hell i'll even donate a DVB-T card to someone.
-------------------------------------------------------------------------
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 prev parent reply other threads:[~2007-05-03 9:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 10:49 udev problem DVB-S/T Cards Razza
2007-05-02 8:47 ` 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 [this message]
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='000a01c78d62$dffcb320$9ff61960$@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.