From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bryan Kadzban <bryan@kadzban.is-a-geek.net>
Date: Thu, 03 May 2007 01:56:02 +0000
Subject: Re: udev problem DVB-S/T Cards
Message-Id: <46394132.8050008@kadzban.is-a-geek.net>
MIME-Version: 1
Content-Type: multipart/mixed; boundary="===============2114067110=="
List-Id: <linux-hotplug.vger.kernel.org>
References: <000301c78982$db8615e0$929241a0$@com>
In-Reply-To: <000301c78982$db8615e0$929241a0$@com>
To: linux-hotplug@vger.kernel.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============2114067110==
Content-Type: multipart/signed; micalg=pgp-ripemd160;
	protocol="application/pgp-signature";
	boundary="------------enigCDBC31AB80B344F9F68AD6BB"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigCDBC31AB80B344F9F68AD6BB
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Razza wrote:
> I have to put my hands up and say, I really don't understand what you
> are saying :o(

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.

> Is the path/node not set by this command ?=20
> NAME=3D"dvb/adapter$env{ID_DVB_ADAPTER}/$env{ID_DVB_DEVICE}"

Yes, it is -- but that rule will use the wrong value for ID_DVB_ADAPTER
and _DEVICE.  Because path_id won't print anything for these devices,
ENV{ID_PATH} will be empty (normally path_id creates it).  And therefore
neither ID_DVB_ADAPTER-setting rule will ever match.

Therefore, the rules will use the fall-back values (which aren't any
different than before).

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.

[1] http://marc.info/?l=3Dlinux-hotplug-devel&m=3D117811269801775&w=3D2


--------------enigCDBC31AB80B344F9F68AD6BB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGOUE5S5vET1Wea5wRA25KAKCiHzdm9XUouZiZGGaPvMLErLnBrwCeNqTJ
9AmtgJcRB1lWrA2nLt7lLFc=
=/ZG6
-----END PGP SIGNATURE-----

--------------enigCDBC31AB80B344F9F68AD6BB--


--===============2114067110==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
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/
--===============2114067110==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
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

--===============2114067110==--