From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Razza" <rjames31@btopenworld.com>
Date: Thu, 03 May 2007 09:10:19 +0000
Subject: RE: udev problem DVB-S/T Cards
Message-Id: <000a01c78d62$dffcb320$9ff61960$@com>
List-Id: <linux-hotplug.vger.kernel.org>
References: <000301c78982$db8615e0$929241a0$@com>
In-Reply-To: <000301c78982$db8615e0$929241a0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

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