Remote Plugin

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



J?rg Schneide wrote:
> Udo Richter schrieb:
> 
> > No. Unless I'm overlooking something important, the official driver
> > still only accepts one address parameter and has only one translation
> > table. It might be some patched driver though.
> 
> What I really don't understand is, why?
> When the debug mode is enabled the driver seems to know the adresses very well,
> so why they can't be used by the plugin?

There is no easy way to pass that information through the input driver
to the plugin. The input driver requires key codes in the range 1..511.

> btw.: I needed hours to find out how to enable the IR-debugging,
> it seems to be documented nowhere. A posting in this list stated it has to
> be enabled with debug=16 as a parameter for dvb_ttpci, that seems to be not
> correct or outdated.

debug=16 is correct for all recent dvb-kernel drivers.

With kernel 2.6.x you can simply type
	echo 16 > /sys/module/dvb_ttpci/parameters/debug

> I found out -more by accident- that the parameter debug_ir=16 
> works.

Wrong, this never worked. Older drivers used av7110_ir_debug=1.

Oliver

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


[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux