Quoting Steffen Barszus <[EMAIL PROTECTED]>:

> Am Mittwoch, 13. August 2003 16:38 schrieb Svetoslav Slavtchev:
> > Quoting Steffen Barszus <[EMAIL PROTECTED]>:
> > > Am Dienstag, 12. August 2003 23:08 schrieb Svetoslav Slavtchev:
> > > > Hi Thomas,
> > > >
> > > > i uploaded mod_dvb-1.0.0 (and i think almost all my 2.4.22.0.2mdk
> > >
> > > patches)
> > >
> > > > to http://varna.demon.co.uk/~svetlio/ruby-contrib/mdk-cook/for_tmb/
> > > >
> > > >
> > > > and the kernel team could also look into them :(
> > >
> > > mod_dvb-1.0.0 is important since it would not make any sense to ship a
> > > PREx
> > >
> > > version. But I guess that applies to other patches on your site too.
> Has
> > > the
> > >
> > > devfsd.conf part of this go to devfsd package ? I would really love to
> > > see having dvb working of the box.
> >
> > the devfsd.conf part ?
> > you mean the module loading & configuration ?
> > this should be done by harddrake probably.
> 
> Dunno. The entries in modules.conf for sure. I base my knowledge mainly on
> the 
> dvb-modules RPM of Guido Draheim. This RPM does work well on 9.1, all the 
> things he has done in there just need to be integrated somehow in 9.2 . 
> 
> He has :
> 
> REGISTER ^dvb/adapter[0-9]+/[^/]+$   PERMISSIONS root.video 0660
> REGISTER ^ost/video[0-9]+$           PERMISSIONS root.video 0660
> REGISTER ^v4l/[^/]+[0-9]+$           PERMISSIONS root.video 0660
> 
> in /etc/devfs/conf.d/dvb-modules.conf .

this should be included in the devfs package, nothing for harddrake here

> If this has to be done with
> harddrake, 
> I will put it in the bugreport on harddrake I want to file once i can 
> actually post something to bugzilla (failed the last days)
> 
> > but you might want to take a look at driver.marvel init script,
> > and tweak it for mod_dvb
> > (i took the idea from driver.mtx /or smth like this/ from linuxtv.org )
> 
> With the allready mentioned entries in /etc/modules.conf etc. it would be 
> enough to modprobe -r dvb-ttpci .

harddrake should add the modules.conf entries

> This will be done inside the runlevelscript

and this should be done automaticaly by devfsd i think
 
> of vdr. The vdr-runlevelscript needs to reload the driver if something bad 
> happened (crash of the firmware and things like that). This is allmost all 
> ready, just some finetuning of it will be done. Loading/reloading/deloading
> 
> of all the modules inside that rc-script would make it a way to complex and
> 
> shouldn't belong to the runlevelscript, but be configured in modules.conf. If
> 
> there is no chance to get it in harddrake for 9.2 , i will need a dirty hack.
> 
best,

svetljo
-- 



Reply via email to