On Thu, 2003-01-16 at 22:34, Klaus Schmidinger wrote: > Andrew de Quincey wrote: > > > > > > * Support on-the-fly configuration in v4l 2 (possibly v4l 1 if I have > > > > the time) > > > > > > > > Reason: I need to have the driver running in the same machines as the > > > > dvb-kernel DVB driver which is v4l2... > > > > > > I don't know if this is a related problem, but maybe, while you're at it, > > > you could fix this: every time I record a Transport Stream from my Kfir card > > > I have to reload the driver, otherwise the next recording will have severe > > > artefacts at the bottom quarter of the picture. When recording PS/PES it works > > > fine without driver reloads - but I do need TS.
When you reload the driver, do you have to reload the firmware, or do you set "loaded=1" so it just uses whatever is already there? Incidentally, I've just noticed there are two sets of firmware for the kfir... the exact one used depends on what type of stream you request: vtv: program vtv1: system vtv2: transport The second set provides the same functionality, but is called "vtv8, vtv18, vtv28". There is code in the driver to switch between them, controlled by this variable "DVB_MODE". However, DVB_MODE is ALWAYS set to 0, so only the first set is used... anyone?? Eek! just noticed the time! Bad Andrew, hacking at 2am again :) -- Andrew de Quincey <[EMAIL PROTECTED]>
