From: Matthias Schwarzott <zzam@gentoo.org>
To: Carsten Meier <cm@trexity.de>
Cc: hermann pitton <hermann-pitton@arcor.de>, linux-media@vger.kernel.org
Subject: Re: Howto obtain sysfs-pathes for DVB devices?
Date: Fri, 30 Jan 2009 12:51:03 +0100 [thread overview]
Message-ID: <200901301251.05258.zzam@gentoo.org> (raw)
In-Reply-To: <20090130121952.787cdf24@tuvok>
On Freitag, 30. Januar 2009, Carsten Meier wrote:
> Am Fri, 30 Jan 2009 03:07:07 +0100
>
> schrieb hermann pitton <hermann-pitton@arcor.de>:
> > Hi,
> >
> > Am Mittwoch, den 28.01.2009, 16:46 +0100 schrieb Carsten Meier:
> > > Hello again,
> > >
> > > now I've managed to obtain syfs-pathes for v4l2-devices. But what
> > > about dvb? I haven't found something like bus_info in the
> > > dvb-api-docs. (I'm new to it) Any hints for this?
> > >
> > > Thanks,
> > > Carsten
> >
> > I'm also still new on it ...
> >
> > Maybe anything useful here?
> >
> > cat /sys/class/dvb/dvb0.frontend0/uevent
> > MAJOR=212
> > MINOR=0
> > PHYSDEVPATH=/devices/pci0000:00/0000:00:08.0/0000:01:07.0
> > PHYSDEVBUS=pci
> > PHYSDEVDRIVER=saa7134
> >
> > Cheers,
> > Hermann
>
> Hi,
>
> IMHO there is no other way (not counting other daemons) than scanning
> the dvb-device-files, stat() them, and compare major and minor numbers
> with sysfs-contents. Anyway, I think I'll switch to HAL for that...
>
One way of asking udev is this:
udevadm info -q path -n /dev/dvb/adapter0/frontend0
Regards
Matthias
next prev parent reply other threads:[~2009-01-30 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 15:46 Howto obtain sysfs-pathes for DVB devices? Carsten Meier
2009-01-30 2:07 ` hermann pitton
2009-01-30 11:19 ` Carsten Meier
2009-01-30 11:51 ` Matthias Schwarzott [this message]
2009-01-30 12:23 ` Carsten Meier
2009-01-30 12:45 ` Matthias Schwarzott
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=200901301251.05258.zzam@gentoo.org \
--to=zzam@gentoo.org \
--cc=cm@trexity.de \
--cc=hermann-pitton@arcor.de \
--cc=linux-media@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