[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ocm9wi3q.fsf@tac.ki.iif.hu>
Date: Tue, 08 Dec 2009 17:22:49 +0100
From: Ferenc Wagner <wferi@...f.hu>
To: Mauro Carvalho Chehab <mchehab@...hat.com>
Cc: Jon Smirl <jonsmirl@...il.com>, Andy Walls <awalls@...ix.net>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Jarod Wilson <jarod@...sonet.com>,
Krzysztof Halasa <khc@...waw.pl>,
Christoph Bartelmus <lirc@...telmus.de>, j@...nau.net,
jarod@...hat.com, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
superm1@...ntu.com
Subject: Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure
Mauro Carvalho Chehab <mchehab@...hat.com> writes:
> Jon Smirl wrote:
>
>> This model is complicated by the fact that some remotes that look
>> like multi-function remotes aren't really multifunction. The remote
>> bundled with the MS MCE receiver is one. That remote is a single
>> function device even though it has function buttons for TV, Music,
>> Pictures, etc.
>
> An unsolved question on my mind is how should we map such IR's? Should
> we provide a way for them to emulate a multifunction IR (for example,
> after pressing TV key, subsequent keystrokes would be directed to the
> TV evdev device?), or should we let this up to some userspace app to
> handle this case?
This case feels similar to that of Caps Lock, Num Lock and Scrool Lock,
but I don't know if that scheme could be applied here.
--
Regards,
Feri.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists