Steffen Barszus <[EMAIL PROTECTED]> writes:

> 1) 
> a devfsd-conf entry :
> 
> REGISTER ^dvb/adapter[0-9]+/[^/]+$   PERMISSIONS root.video 0660
> REGISTER ^v4l/[^/]+[0-9]+$           PERMISSIONS root.video 0660

this should be safe to include in std devfsd
what do you have in /dev/v4l/ ?
is the /dev/video link still created with the above patch ?
 
> 2) 
> harddrake pci-id's:
> 
> grep dvb-ttpci modules.pcimap in /lib/modules/`uname -r` 
> 
> harddrake has to add the /etc/modules.conf entry
> ---------------------------------------------------
> probeall /dev/dvb dvb-ttpci
> alias /dev/dvb/* /dev/dvb
> below dvb-ttpci alps_bsrv2 alps_tdmb7 alps_tdlb7
> add below dvb-ttpci grundig_29504-401 grundig_29504-491
> add below dvb-ttpci stv0299 ves1820
> options dvb-ttpci latency=128
> 
> # comment the following out if you want to use dvb-net
> options dvb-core dvb_shutdown_timeout=5
> 
> # adapt the following to your needs and comment it in if you need it
> #post-install dvb-ttpci /path/to/av7110_loadkeys [options]
> ------------------------------------------------------

pixel, can drakx add this if above test success ?
 
> av7110_loadkeys is in the linuxtv-dvb-1.0.0 driver package, as well
> as some other usefull tools (scan => channelscan, [ts]zap )

if we want drakx support, we need to have this in std install.
warly ?


Reply via email to