[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B1EE9A7.70609@redhat.com>
Date: Tue, 08 Dec 2009 22:04:55 -0200
From: Mauro Carvalho Chehab <mchehab@...hat.com>
To: Krzysztof Halasa <khc@...waw.pl>
CC: Jon Smirl <jonsmirl@...il.com>, Andy Walls <awalls@...ix.net>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Jarod Wilson <jarod@...sonet.com>,
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
Krzysztof Halasa wrote:
> Jon Smirl <jonsmirl@...il.com> writes:
>
>> Why do you want to pull the 1KB default mapping table out of the
>> device driver __init section and more it to a udev script? Now we will
>> have to maintain a parallel udev script for ever receiver's device
>> driver.
>
> Of course no. We will need a single program (script etc.) for all
> devices. And we will need a database of the known remotes (scan and key
> codes).
The keycode database can be easily extracted from kernel drivers by script.
I have it already at V4L/DVB development tree.
>> You can handle that with __devinit
>
> __devinit is NOP with hot-plug.
>
> Fortunately we don't need the keymaps in the kernel.
> For certain uses we may (and may not) need to have one keymap built-in,
> perhaps something similar to the embedded initrd.
I still think the better is to have them in kernel, but compiled only
if selected at Kbuild.
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