On Tue, Nov 9, 2010 at 1:32 AM, Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> wrote: > On Mon, Nov 08, 2010 at 12:14:48PM -0200, Mauro Carvalho Chehab wrote: >> Em 08-11-2010 11:41, jonsmirl@xxxxxxxxx escreveu: >> > On Mon, Nov 8, 2010 at 8:34 AM, jonsmirl@xxxxxxxxx <jonsmirl@xxxxxxxxx> wrote: >> >> To achieve plug and play at least one of four choices has to happen: >> > >> > There is another option, the IR maps get integrated into user space >> > keyboard mapping package. This may be possible with the new >> > libxkbcommon package. >> >> That seems interesting. >> > > I disagree here. libxkbcommon provides X interface while applications You are assuming that libxkbcommon stays X specific. I'm pushing to turn it into a generic keymapping solution. Wayland sure doesn't want to inherit all of the baggage of X keymaps. This is also an opportunity to address internationalization at the console level. This is an opportunity to clean up the whole key mapping mess in user space. Writing a generic keymapping library is a good project if someone is looking for something to do. It's not too complicated since you can use libxkbcommon as guidance. > might want to access evdev nodes directly. If anything, parts of > ir-utils dealing with keymap selection should be moved into udev. Maybe > we should split utilities that select protocol from the keymap setting > and use udev keymap utilities to do the task. > > Thanks. > > -- > Dmitry > -- Jon Smirl jonsmirl@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
