[vdr] [ANNOUNCE] dynamite plugin

L. Hanisch dvb at flensrocker.de
Fri Mar 25 01:47:14 CET 2011


Am 24.03.2011 01:57, schrieb syrius.ml at no-log.org:
> questions :
> - have you considered changing the way vdr detects adapter on startup ?
>    for instance vdr won't detect /dev/dvb/adapter1 if
>    /dev/dvb/adapter0 does not exist. this might happen when using udev
>    rules and restarting vdr while a module isn't loaded

dynamite 0.0.6 now uses udev device enumeration to detect all dvb frontends regardless of their numbering.
If you would like to keep an adapter from being used by vdr you can set an udev environment property on that device.

The following would ensure that /dev/dvb/adapter2/frontend* is not attached:

  ACTION=="add", SUBSYSTEM=="dvb", ENV{DVB_ADAPTER_NUM}=="2", ENV{dynamite_attach}="no"

This acts as an replacement for the "-D" option of the core vdr. Since the card index of dynamically attached devices 
are not necessarily related to their adapter number it wouldn't work as expected any more.
(the -D option is only used in the vdr internal dvb device enumeration - if you add a device afterwards it would get 
attached even if it gets a "forbidden" adapter nr)

If you run multiple instances of vdr with different ids (option -i) you can associate the devices to the different vdrs 
with the property "dynamite_instanceid".

This attaches /dev/dvb/adapter2/frontend* to "vdr -i 1" and all other adapter to "vdr -i 0":

ACTION=="add", SUBSYSTEM=="dvb", ENV{DVB_ADAPTER_NUM}!="2", ENV{dynamite_instanceid}="0"
ACTION=="add", SUBSYSTEM=="dvb", ENV{DVB_ADAPTER_NUM}=="2", ENV{dynamite_instanceid}="1"


More information about the vdr mailing list