[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0912121401500.3370@asgard.lang.hm>
Date: Sat, 12 Dec 2009 14:04:16 -0800 (PST)
From: david@...g.hm
To: Krzysztof Halasa <khc@...waw.pl>
cc: Devin Heitmueller <dheitmueller@...nellabs.com>,
Christoph Bartelmus <lirc@...telmus.de>,
dmitry.torokhov@...il.com, j@...nau.net, jarod@...hat.com,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, mchehab@...hat.com, 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
On Mon, 23 Nov 2009, Krzysztof Halasa wrote:
> Devin Heitmueller <dheitmueller@...nellabs.com> writes:
>
>> There is an argument to be made that since it may be desirable for
>> both IR receivers and transmitters to share the same table of remote
>> control definitions, it might make sense to at least *consider* how
>> the IR transmitter interface is going to work, even if it is decided
>> to not implement such a design in the first revision.
>>
>> Personally, I would hate to see a situation where we find out that we
>> took a bad approach because nobody considered what would be required
>> for IR transmitters to reuse the same remote control definition data.
>
> I briefly though about such possibility, but dismissed it with
> assumption that we won't transmit the same codes (including "key" codes)
> that we receive.
>
> Perhaps I'm wrong.
I could definantly see this happening. the computer receives the 'play'
button from a dvd remote, issues commands to control the audio system, dim
lights, and then sends the 'play' button to the DVD player inside a
cabinet where it can't see the remote directly.
but in any case, it shouldn't be hard to share a table of mappings.
David Lang
--
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