Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(if free)
|
|
has nothing to do with dynamite, just to get rid of hard coded sys paths
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You can use the udev property "dynamite_ignore" to preserve a device from being attached.
With the udev property "dynamite_instanceid" the devices can be associated with different vdr instances.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
any receivers or locks
|
|
arguments
- raise event via cPlugin::Service if a device is attached/detached so other plugins
can react on it ("dynamite-event-DeviceAttached-v0.1", "dynamite-event-DeviceDetached-v0.1")
|
|
|
|
|
|
|
|
|
|
|
|
set voltage only on the devices which are allowed to
|
|
|
|
- while in cDvbDeviceProbe create only as much cDynamicDevice-objects as needed
- create dummy-device-probe only if specified on command line option "--dummy-probe"
|
|
|
|
Now they are recognized on devices present at startup.
|
|
|
|
|
|
dvbdevices should close all their handles and can't be used for epg-scan.
So be careful to not disable all devices or you won't get epg.
A timer or channel-switch should reactivate the device (hopefully).
|
|
|
|
|
|
|
|
In setup.conf set dynamite.GetTSTimeoutHandler to a program you want
to execute. If the udev-property dynamite_timeout_handler_arg is set it will
be passed as the argument to it otherwise the devpath with wich the device was
attached to dynamite.
|