Skip to contentSkip to conversation

Howto obtain sysfs-pathes for DVB devices?

DISCUSSION Carsten Meier 3 participants 6 messages Jan 28, 2009 – Jan 30, 2009 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw

Hi,

Am Mittwoch, den 28.01.2009, 16:46 +0100 schrieb Carsten Meier:

Quoted 8 lines

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

#2 lore raw

Am Fri, 30 Jan 2009 03:07:07 +0100
schrieb hermann pitton <[email protected]>:

Quoted 23 lines

Hi,

Am Mittwoch, den 28.01.2009, 16:46 +0100 schrieb Carsten Meier:

Quoted 8 lines

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

Quoted 3 lines

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...

Cheers,
Carsten

#3 lore raw
Quoted 26 lines · Carsten Meier

Am Fri, 30 Jan 2009 03:07:07 +0100

schrieb hermann pitton <[email protected]>:

Quoted 23 lines

Hi,

Am Mittwoch, den 28.01.2009, 16:46 +0100 schrieb Carsten Meier:

Quoted 8 lines

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

Quoted 9 lines
Quoted 2 lines

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

#4 lore raw

Am Fri, 30 Jan 2009 12:51:03 +0100
schrieb Matthias Schwarzott <[email protected]>:

Quoted 38 lines · Carsten Meier
Quoted 29 lines

Am Fri, 30 Jan 2009 03:07:07 +0100

schrieb hermann pitton <[email protected]>:

Quoted 23 lines

Hi,

Am Mittwoch, den 28.01.2009, 16:46 +0100 schrieb Carsten Meier:

Quoted 8 lines

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

Quoted 2 lines

Cheers,
Hermann

Quoted 7 lines

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...

Quoted 5 lines

One way of asking udev is this:
udevadm info -q path -n /dev/dvb/adapter0/frontend0

Regards
Matthias

Ok, then I think I'm gonna use it... :) It's much more simple than struggling through dbus-/hal-libs and the various unfinished c++ bindings, although I normally don't like to start system-tools from c++. Or is there any c-api for it? I haven't found one.

Thanks,
Carsten

#5 lore raw
Quoted 5 lines · Carsten Meier

Am Fri, 30 Jan 2009 12:51:03 +0100

Quoted 4 lines

One way of asking udev is this:
udevadm info -q path -n /dev/dvb/adapter0/frontend0

Quoted 8 lines
Quoted 2 lines

Regards
Matthias

Ok, then I think I'm gonna use it... :) It's much more simple than struggling through dbus-/hal-libs and the various unfinished c++ bindings, although I normally don't like to start system-tools from c++. Or is there any c-api for it? I haven't found one.

There is a in development version of libudev contained since udev-127. But its API is not yet stable I think.

Regards
Matthias