[lkml]   [2007]   [May]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Input: document the proper usage of EV_KEY and KEY_UNKNOWN
    On Thu, May 31, 2007 at 07:28:14PM -0300, Henrique de Moraes Holschuh wrote:
    > We have all the pieces needed to have sane, generic userland keyboard handling
    > in place for a while now, but it was not sufficiently documented (or used!).
    > If EV_KEY input drivers always generate scan codes that can be used to
    > reprogram their keycode maps, and always generate EV_MSC MSC_SCAN events when
    > they output an EV_KEY KEY_UNKNOWN event, userspace can trap those and feed it
    > to a generic helper that can ask the user to assign a key code and function to
    > that key.

    I still disagree that this is the best approach. Userspace already has
    the functionality to map keys if they produce a keycode. Producing
    KEY_UNKNOWN would require the implementation of a stack of extra code.

    Matthew Garrett |
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-06-01 01:37    [W:0.023 / U:6.512 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site