[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B0ECF1B.1090103@redhat.com>
Date: Thu, 26 Nov 2009 16:55:23 -0200
From: Mauro Carvalho Chehab <mchehab@...hat.com>
To: Krzysztof Halasa <khc@...waw.pl>
CC: Christoph Bartelmus <lirc@...telmus.de>, jarod@...sonet.com,
awalls@...ix.net, 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,
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
Krzysztof Halasa wrote:
> Mauro Carvalho Chehab <mchehab@...hat.com> writes:
>
>> 1) the developer that adds the hardware also adds the IR code. He has
>> the hardware and the IR for testing, so it means a faster development
>> cycle than waiting for someone else with the same hardware and IR to
>> recode it on some other place. You should remember that not all
>> developers use lirc;
>
> It's fine, but please - no keymaps in the kernel (except for fixed
> receivers, i.e. the ones which can only work with their own dedicated
> remote, and which don't pass RC5/etc. code).
>
> The existing keymaps (those which can be used with lirc) have to be
> moved to userspace as well.
The removal of the existing keymaps from kernel depends on having an application
to be called from udev to load the proper keymaps when a device is probed.
After having it for a while, we should deprecate the in-kernel keymaps
and move them to userspace.
I also think that it is important to remove the 7 bits limitation from all drivers
and re-generate the keymaps, since they'll change after it.
cheers,
Mauro.
--
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