Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure

2009-11-23 Thread Emmanuel Fusté
It is perhaps time to resurrect Jon Smirl's work about In-kernel IR remote control support ? See http://marc.info/?l=linux-kernelm=122591465821297w=2 and all discussions around it. Regards, Emmanuel. ---

Re: [RFC v2] Another approach to IR

2009-12-03 Thread Emmanuel Fusté
Jon Smirl wrote: On Wed, Dec 2, 2009 at 11:13 PM, Jarod Wilson ja...@wilsonet.com 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. I

Re: [RFC v2] Another approach to IR

2009-12-03 Thread Emmanuel Fusté
Em Thu, 3 Dec 2009 11:50:04 -0500 Jon Smirl jonsm...@gmail.com escreveu: On Thu, Dec 3, 2009 at 11:33 AM, Mauro Carvalho Chehab mche...@redhat.com wrote: Ferenc Wagner wrote: Mauro Carvalho Chehab mche...@redhat.com writes: Dmitry Torokhov wrote: The interesting thing is that

Re: [RFC v2] Another approach to IR

2009-12-03 Thread Emmanuel Fusté
On Thu, Dec 03, 2009 at 02:33:56PM -0200, Mauro Carvalho Chehab wrote: Ferenc Wagner wrote: Mauro Carvalho Chehab mche...@redhat.com 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.

Re: [RFC] What are the goals for the architecture of an in-kernel IR system?

2009-12-08 Thread Emmanuel Fusté
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