Hi,
Stefan Lucke schrieb:
>>> Same here.
>>> Which DVB-T device do you use ? I'm using a cinergyT2.
>>>
>>> Ioctl's for this device are not passed
>>> via the common frontend interface. The new "API" has to get
>>> integrated into the cinergyT2 driver or client programs like vdr etc.
>>> have to
On Saturday 12 January 2008, Morfsta wrote:
> On Jan 12, 2008 3:37 PM, Stefan Lucke <[EMAIL PROTECTED]> wrote:
> > Same here.
> > Which DVB-T device do you use ? I'm using a cinergyT2.
> >
> > Ioctl's for this device are not passed
> > via the common frontend interface. The new "API" has to get
> >
On Jan 12, 2008 3:37 PM, Stefan Lucke <[EMAIL PROTECTED]> wrote:
> Same here.
> Which DVB-T device do you use ? I'm using a cinergyT2.
>
> Ioctl's for this device are not passed
> via the common frontend interface. The new "API" has to get
> integrated into the cinergyT2 driver or client programs l
On Saturday 12 January 2008, Morfsta wrote:
> Hi,
>
> Thanks for speaking with Marco, Reinhard - its appreciated.
>
> Unfortunately, the patch does not fix the problem. Still no picture on
> DVB-T transmissions.
Same here.
Which DVB-T device do you use ? I'm using a cinergyT2.
Ioctl's for this
Hi,
Thanks for speaking with Marco, Reinhard - its appreciated.
Unfortunately, the patch does not fix the problem. Still no picture on
DVB-T transmissions.
Regards
On Jan 11, 2008 7:21 PM, Reinhard Nissl <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Reinhard Nissl schrieb:
>
> > So it seems to me that e
Hi list,
I've improved the hard link cutter patch. The new 0.2.0 version has
support for multiple /videoXX folders. The new patch tries to find a
compatible /videoXX folder that can hold a hard link for each file. Deep
mounted video folders (like mount to /video/nfs-server/ or
/video/usb-disk
On Saturday 12 January 2008, Reinhard Nissl wrote:
> Ville Skyttä schrieb:
>
> > Also, somewhat off topic: when running powertop[1] on my VDR box, I see
> > lircd waking up the CPU from idle about 1000 times a second while VDR is
> > connected to it:
> >
> > Top causes for wakeups:
> > 54.3% (988
Hi,
Ville Skyttä schrieb:
>> I think, the LIRC protocol misses a timestamp for each button
>> press. Or an even more favorable solution would be to put the
>> timeout and frequency processing into LIRC and have VDR to
>> process each key as it arrives, just like with the KBD remote.
>
> Would us
On Saturday 12 January 2008, Reinhard Nissl wrote:
> I think, the LIRC protocol misses a timestamp for each button
> press. Or an even more favorable solution would be to put the
> timeout and frequency processing into LIRC and have VDR to
> process each key as it arrives, just like with the KBD r
Hello vdr readers,
is there a possibility to contact the femon-plugin developer? I want
to give any feature request for make the femon plugin accessible for
braille users.
--
Best regards Sebastian
ICQ: 264706583 | MSM: [EMAIL PROTECTED] | Skype: sebo_de | Yahoo: de_sebo
E-Mail: [EMAIL PROTECTED
10 matches
Mail list logo