[vdr] lirc key reading to slow ? Buffer overflow ?

2010-12-04 Thread Steffen Barszus
Hi !

i get these errors, once my remote is doing key repeats:

Dec  3 23:33:13 vdr vdr: [24629] ERROR: unparseable lirc command:
gy_Receiver-event-kbd#012b-Gyration_Gyration_RF_Technology_Receiver-event-kbd#01272
0 KEY_VOLUMEDOWN usb-Gyration_Gyration_RF_TechnoloKEY_VOLUMEDOWN Dec  3
23:34:14 vdr vdr: last message repeated 583 times

especially note the 
usb-Gyration_Gyration_RF_TechnoloKEY_VOLUMEDOWN
and ...kbd#012b- (this should read usb-...) 

is there anything forgot to reset ? A buffer to small ? 
Just wrong how it is read ? In irw and xbmc there
seems no such issue, means the repeat just works. 

i increased the buffers to:

private:
  enum { LIRC_KEY_BUF = 500, LIRC_BUFFER_SIZE = 4096 };

which seems to make the error disappear, but its still incredible slow
(compared to other applications) in accept the keys. Can this be
improved ? 


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] Minor *.po patch

2010-12-04 Thread Tobias Grimm
The gettext version I use automatically adds a Language field to the
headers of the po-Files. It would be nice to have this field there in
the first place, so here's a small patch that adds it.

Tobias




99_add-language-to-po.dpatch
Description: application/shellscript
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] dvb devices on demand patch

2010-12-04 Thread Steffen Barszus
Hi !

i just read up again on this:
http://www.mail-archive.com/vdr@linuxtv.org/msg13224.html

Actually i think this would be also a good starting for 

a) save some energy - if DVB devices are not opened all the time, the
driver has the chance to put it into standby saving some heat, energy
and lifetime of the cards

b) have a beginning of dvb device hotplug - if dvb devices are
discovered on demand, its a good chance at a later stage to also add
and remove cards on the fly. There is sure some notification required
from udev to vdr so it can keep internal reference of the how many
devices are there. 

Not that i could help in doing this - being aware it might take a while
until its finished -  but i still thought to share my thoughts, that
this addition is not only usefull for shared frontends, but also for
general usage. 

Hope the work on this is continued and possibly accepted by Klaus after
some review and as work in progress. 

Kind Regards

Steffen

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] dvb devices on demand patch

2010-12-04 Thread VDR User
On Sat, Dec 4, 2010 at 4:24 AM, Steffen Barszus
steffenbpu...@googlemail.com wrote:
 a) save some energy - if DVB devices are not opened all the time, the
 driver has the chance to put it into standby saving some heat, energy
 and lifetime of the cards

There are a couple cards that consume a lot of power iirc so this
could actually be useful for users of those cards.  But what about
performance/lag?  And also how healthy is it to constantly put a
device in and out of standby?

 b) have a beginning of dvb device hotplug - if dvb devices are
 discovered on demand, its a good chance at a later stage to also add
 and remove cards on the fly. There is sure some notification required
 from udev to vdr so it can keep internal reference of the how many
 devices are there.

I wonder if this is actually useful.  Is there anyone that would
need/want this in the real world?

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] dvb devices on demand patch

2010-12-04 Thread Tony Houghton

On 04/12/10 18:09, VDR User wrote:

On Sat, Dec 4, 2010 at 4:24 AM, Steffen Barszus
steffenbpu...@googlemail.com  wrote:

b) have a beginning of dvb device hotplug - if dvb devices are
discovered on demand, its a good chance at a later stage to also add
and remove cards on the fly. There is sure some notification required
from udev to vdr so it can keep internal reference of the how many
devices are there.


I wonder if this is actually useful.  Is there anyone that would
need/want this in the real world?


I can imagine a situation where you're already recording one or more
programmes with your internal card, then realise you want to
watch/record something else on a different channel and you forgot to
plug your USB receiver back in after you took it away to use with your
laptop...

--
TH * http://www.realh.co.uk

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] dvb devices on demand patch

2010-12-04 Thread Gerald Dachs
Am Sat, 4 Dec 2010 10:09:42 -0800
schrieb VDR User user@gmail.com:

  b) have a beginning of dvb device hotplug - if dvb devices are
  discovered on demand, its a good chance at a later stage to also add
  and remove cards on the fly. There is sure some notification
  required from udev to vdr so it can keep internal reference of the
  how many devices are there.
 
 I wonder if this is actually useful.  Is there anyone that would
 need/want this in the real world?

In which world did you live the last months ;) ? Sorry, I couldn't
insist. 

Our VDR-Distribution yaVDR is optimized for a short boot. With old
fashioned PCI cards you can get down to 6 seconds boot time since grub,
but if one of our user decides to buy another p. e. usb device, we
have to delay the boot up to 30 seconds to allow the usb device to get
ready. With device hotplugging there would be no need to wait for this
device and the user would already see tv 30 seconds earlier. Believe me
there are users that thinks this matters.

Gerald

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] dvb devices on demand patch

2010-12-04 Thread VDR User
On Sat, Dec 4, 2010 at 11:37 AM, Gerald Dachs v...@dachsweb.de wrote:
 Am Sat, 4 Dec 2010 10:09:42 -0800
 schrieb VDR User user@gmail.com:

  b) have a beginning of dvb device hotplug - if dvb devices are
  discovered on demand, its a good chance at a later stage to also add
  and remove cards on the fly. There is sure some notification
  required from udev to vdr so it can keep internal reference of the
  how many devices are there.

 I wonder if this is actually useful.  Is there anyone that would
 need/want this in the real world?

 In which world did you live the last months ;) ? Sorry, I couldn't
 insist.

 Our VDR-Distribution yaVDR is optimized for a short boot. With old
 fashioned PCI cards you can get down to 6 seconds boot time since grub,
 but if one of our user decides to buy another p. e. usb device, we
 have to delay the boot up to 30 seconds to allow the usb device to get
 ready. With device hotplugging there would be no need to wait for this
 device and the user would already see tv 30 seconds earlier. Believe me
 there are users that thinks this matters.

I'm a fan of short boot times.  Are there that many users that are
power cycling their pc's frequently?  Of all the pc's I use be them
Windows or Linux, work or personal, hardly any of them are rebooted.
Really only my test boxes (which are intended) or in the event of a
power loss or so due to very bad weather.  Of course that's just my
usage and everybody has their own.  I just don't see that this is a
situation that's even remotely common.

I'm not for or against the idea.  I just wonder if there's significant
need to distract Klaus away from other things people have been
needing/wanting for quite a long time.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr