From: "Razza" <rjames31@btopenworld.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: udev problem DVB-S/T Cards
Date: Wed, 02 May 2007 23:48:21 +0000 [thread overview]
Message-ID: <000d01c78d14$5e34a800$1a9df800$@com> (raw)
In-Reply-To: <000301c78982$db8615e0$929241a0$@com>
Bryan Kadzban wrote on 02 May 2007 23:21:
> Razza wrote:
> > Have I missed something?
>
> You need to add support for DVB devices to path_id, but other than that
> I don't think so.
>
> After you add support (or if you already have), then you will want to
> make sure the right ID_PATH value is printed by path_id when run
> manually. You will need to give path_id the devpath of the device file
> (which is what "udevinfo -q path" prints).
Sorry I am not a Linux expert, in fact definitely rank of super newbie!
I have to put my hands up and say, I really don't understand what you are
saying :o(
Is the path/node not set by this command ?
NAME="dvb/adapter$env{ID_DVB_ADAPTER}/$env{ID_DVB_DEVICE}"
-------------------------------------------------------------------------
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-02 23:48 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 [this message]
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='000d01c78d14$5e34a800$1a9df800$@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 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).