Re: ir-core and default IR maps

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Sat, Nov 06, 2010 at 06:08:57PM -0400, jonsmirl@gmail.com wrote:
> I thought about this some more and I think the default maps should
> stay in the drivers. The maps are marked __init so they don't take any
> room after they are loaded. This is an important piece and plug and
> play and we should keep it. Only the keymaps for default remote
> controls that ship with the specific hardware should be included in
> the driver. All other keymaps are in user space.
> 

Plug and play does not have to be implemented in kernel and udev is
perfectly capable doing it in userspace for us. Embedded products that
absolutely not want to ship udev and want to limit themselves to a
single vendor-supplied remote will have to adjust their startup scripts
to load the proper keymap.

Keymap in the kernel are needed for devices that are required to boot
(keyboards) - and even then it might be only basic keymap, not the full
multimedia goodness with 300+ distinct keys. I am not accepting any new
mappings for AT keyboard driver and I believe both I and Jiri would like
to delete bunch of HID sub-drivers that only do key remapping.

Attempting to keep keymaps in several places will likely cause them to
diverge, makes user confused where changes should be applied and who is
the authoritative source is, that is why it makes sense to remove them
from the kernel.

Thanks.

-- 
Dmitry