Dmitry Torokhov a écrit :
On Mon, Dec 07, 2009 at 06:54:39PM +0100, Emmanuel Fusté wrote:
Mauro Carvalho Chehab wrote:
In summary,
While the current EVIO[G|S]KEYCODE works sub-optimally for scancodes up
to 16 bytes
(since a read loop for 2^16 is not that expensive), the current
Mauro Carvalho Chehab wrote:
In summary,
While the current EVIO[G|S]KEYCODE works sub-optimally for scancodes up to 16
bytes
(since a read loop for 2^16 is not that expensive), the current approach
won't scale with bigger scancode spaces. So, it is needed expand it
to work with bigger scancod
On Thu, Dec 03, 2009 at 02:33:56PM -0200, Mauro Carvalho Chehab wrote:
> Ferenc Wagner wrote:
> > Mauro Carvalho Chehab writes:
>
> We should not forget that simple IR's don't have any key to select the address,
> so the produced codes there will never have KEY_TV/KEY_DVD, etc.
Wait, wait, KE
Em Thu, 3 Dec 2009 11:50:04 -0500
Jon Smirl escreveu:
> On Thu, Dec 3, 2009 at 11:33 AM, Mauro Carvalho Chehab
> wrote:
> > Ferenc Wagner wrote:
> >> Mauro Carvalho Chehab writes:
> >>
> >>> Dmitry Torokhov wrote:
> >>>
> >
> >> The interesting thing is that input.h defines KEY_TV, KEY_PC, KE
Jon Smirl wrote:
> On Wed, Dec 2, 2009 at 11:13 PM, Jarod Wilson wrote:
>> On Dec 2, 2009, at 9:48 PM, Trent Piepho wrote:
>> ...
>> Now I understand that if 2 remotes send completely identical signals we
>> won't be able to separate them, but in cases when we can I think we
>> should
It is perhaps time to resurrect Jon Smirl's work about In-kernel IR remote
control support ?
See http://marc.info/?l=linux-kernel&m=122591465821297&w=2 and all discussions
around it.
Regards,
Emmanuel.
---
Laposte
