[Patch] text2skin plugins & no OSD with libfreetype6 2.2

Hi,

The attached patch file fix the text2skin plugin which doesn't display
OSD text when it's linking with libfreetype6 2.2

Best Regards,

Jerome

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [Patch] text2skin plugins & no OSD with libfreetype6 2.2

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Bug in SVDRP-hosts-parser

Hi Klaus,

i found a bug in the computing of the Netmask for the SVDRP-Hosts-file.
The byte order in your case was not correctly computed.
Here is a patch.

============= snip ==========
--- config.c.orig       2006-07-01 16:53:25.000000000 +0200
+++ config.c    2006-07-01 16:53:33.000000000 +0200
 <at>  <at>  -106,8 +106,10  <at>  <at> 
      *(char *)p = 0; // yes, we know it's 'const' - will be restored!
      if (m == 0)
         mask = 0;
-     else
-        mask >>= (32 - m);
+     else {
+        mask <<= (32 - m);
+       mask = htonl(mask);
+       }
      }
   int result = inet_aton(s, &addr);
   if (p)
============= snip ==========

Greets
Patrick

--

-- 
     There are only 10 kind of people who understand binary digits:
     Those who do - Those who don't...

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Question about log

Hi,

According to man pages VDR uses by default the highest level of logging.
I didn't change the level but still VDR did not put log anything when
TVOnScreen plugin crashed (crashed because there was no EPG data on any
channel and enter was pressed few times).

Did the plugin crash caused segfault to VDR thus no logging was possible
or am I missing something?

Br, Pasi

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Question about log

I demand that Pasi Juppo may or may not have written...

> According to man pages VDR uses by default the highest level of logging. I
> didn't change the level but still VDR did not put log anything when
> TVOnScreen plugin crashed (crashed because there was no EPG data on any
> channel and enter was pressed few times).

> Did the plugin crash caused segfault to VDR thus no logging was possible or
> am I missing something?

Probably the best thing to do is to get it to dump core.

--

-- 
| Darren Salt    | linux or ds at              | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
|   Let's keep the pound sterling

The Green Midget Cafe, Bromley. Home to Spam and occasional Viking hordes.

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: ATi Remote key repeat

Chris Jones wrote:
> Hi
> 
> On Wed, 2006-06-28 at 01:28 +0200, Oliver Endriss wrote:
> > Please try the evtest tool from the dvb-apps package and
> > post its output for a short key press and for a long one.
> 
> Here is the output. I pressed the play button in both cases:
> 
> cmsj <at> tenshu:~$ evtest /dev/input/event4
> Input driver version is 1.0.0
> Input device ID: bus 0x3 vendor 0xbc7 product 0x4 version 0x100
> Input device name: "X10 Wireless Technology Inc USB Receiver"
> Supported events:
>   Event type 0 (Reset)
>     Event code 0 (Reset)
>     Event code 1 (Key)
>     Event code 2 (Relative)
> ...
> Testing ... (interrupt to exit)
> Event: time 1151653959.792243, type 1 (Key), code 207 (?), value 1
> Event: time 1151653959.792246, type 1 (Key), code 207 (?), value 0
> Event: time 1151653959.792248, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1151653959.880230, type 1 (Key), code 207 (?), value 1
> Event: time 1151653959.880233, type 1 (Key), code 207 (?), value 0
> Event: time 1151653959.880235, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1151653959.928229, type 1 (Key), code 207 (?), value 1
> Event: time 1151653959.928232, type 1 (Key), code 207 (?), value 0
> Event: time 1151653959.928234, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1151653959.976214, type 1 (Key), code 207 (?), value 1
> Event: time 1151653959.976218, type 1 (Key), code 207 (?), value 0
> Event: time 1151653959.976220, type 0 (Reset), code 0 (Reset), value 0

> Event: time 1151653964.559472, type 1 (Key), code 207 (?), value 1
> Event: time 1151653964.559476, type 1 (Key), code 207 (?), value 0
> Event: time 1151653964.559478, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1151653964.607473, type 1 (Key), code 207 (?), value 1
> Event: time 1151653964.607477, type 1 (Key), code 207 (?), value 0
> Event: time 1151653964.607479, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1151653964.743449, type 1 (Key), code 207 (?), value 1
> Event: time 1151653964.743453, type 1 (Key), code 207 (?), value 0
> Event: time 1151653964.743455, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1151653964.791438, type 1 (Key), code 207 (?), value 1
> Event: time 1151653964.791443, type 1 (Key), code 207 (?), value 0
> Event: time 1151653964.791445, type 0 (Reset), code 0 (Reset), value 0
> ...
> Event: time 1151653965.991242, type 1 (Key), code 207 (?), value 1
> Event: time 1151653965.991246, type 1 (Key), code 207 (?), value 0
> Event: time 1151653965.991248, type 0 (Reset), code 0 (Reset), value 0
> Event: time 1151653966.039234, type 1 (Key), code 207 (?), value 1
> Event: time 1151653966.039237, type 1 (Key), code 207 (?), value 0
> Event: time 1151653966.039239, type 0 (Reset), code 0 (Reset), value 0

This driver is terribly broken! Key repeat does not work correctly.
A correct driver would send for a single short press:

> Event: time 1151653964.791438, type 1 (Key), code 207 (?), value 1
> Event: time 1151653964.791443, type 1 (Key), code 207 (?), value 0

For a long press:

> Event: time 1151653964.559472, type 1 (Key), code 207 (?), value 1
> Event: time 1151653964.607473, type 1 (Key), code 207 (?), value 2
> ...
> Event: time 1151653964.743449, type 1 (Key), code 207 (?), value 2
> Event: time 1151653964.743453, type 1 (Key), code 207 (?), value 0

I omitted Reset events, as I don't know what they are used for.
Reset events seem to be ok. The keyboard driver generates them, too.

There is a bug in the remote plugin. It misinterprets Reset as a key
release. Reset should be ignored. Please try the attached patch.

Oliver

--

-- 
--------------------------------------------------------
VDR Remote Plugin available at
http://www.escape-edv.de/endriss/vdr/
--------------------------------------------------------

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: ATi Remote key repeat

Hi

On Sun, 2006-07-02 at 21:07 +0200, Oliver Endriss wrote:
> This driver is terribly broken! Key repeat does not work correctly.
> A correct driver would send for a single short press:

Should I report this upstream to the kernel?

> There is a bug in the remote plugin. It misinterprets Reset as a key
> release. Reset should be ignored. Please try the attached patch.

I applied it, rebuilt the remote module and restarted vdr, but it
doesn't seem to have made a huge difference, but is that just because
the kernel is spewing way too many events?

Cheers,
--

-- 
Chris Jones
  cmsj <at> tenshu.net
   www.tenshu.net

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: ATi Remote key repeat

On Sun, Jul 02, 2006 at 11:26:22PM +0100, Chris Jones wrote:
> On Sun, 2006-07-02 at 21:07 +0200, Oliver Endriss wrote:
> > This driver is terribly broken! Key repeat does not work correctly.
> > A correct driver would send for a single short press:
> 
> Should I report this upstream to the kernel?

Yes.

> > There is a bug in the remote plugin. It misinterprets Reset as a key
> > release. Reset should be ignored. Please try the attached patch.
> 
> I applied it, rebuilt the remote module and restarted vdr, but it
> doesn't seem to have made a huge difference, but is that just because
> the kernel is spewing way too many events?

The patch would only make a difference if the kernel didn't send any
bogus release events.  The patch was necessary for the cx88 remote,
because otherwise the remote plugin would convert each repeat event
to a new key press event.

	Marko

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

VDR starts VPS recording on status 2 (StartsInAFewSeconds)

Hello,

to my understanding of the standard, the status 2 
shall be used to set the recording device into a state,
in which a recording can start immediately
(e.g. power up the harddisk).
The recording itself shall start on status 4.
In my special case I now have advertisments at the beginning
of the recording, which were not recorded when status 2
was not used.

Regards
O. Holler

--

-- 

Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

streamdev for vdr 1.4.0

Hi All,

Where could I find latest streamdev plugin for vdr 1.4.0. I don't have
cvs access, as said in VDR wiki, it require password from me.

With the best wishes.

John.

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr