1. 13 Oct, 2012 1 commit
  2. 08 Mar, 2012 1 commit
    • Alan Cox's avatar
      vt:tackle kbd_table · 079c9534
      Alan Cox authored
      Keyboard struct lifetime is easy, but the locking is not and is completely
      ignored by the existing code. Tackle this one head on
      - Make the kbd_table private so we can run down all direct users
      - Hoick the relevant ioctl handlers into the keyboard layer
      - Lock them with the keyboard lock so they don't change mid keypress
      - Add helpers for things like console stop/start so we isolate the poking
        around properly
      - Tweak the braille console so it still builds
      There are a couple of FIXME locking cases left for ioctls that are so hideous
      they should be addressed in a later patch. After this patch the kbd_table is
      private and all the keyboard jiggery pokery is in one place.
      This update fixes speakup and also a memory leak in the original.
      Signed-off-by: default avatarAlan Cox <alan@linux.intel.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  3. 14 Jun, 2009 1 commit
  4. 14 Apr, 2008 1 commit
  5. 19 Oct, 2007 1 commit
    • Samuel Thibault's avatar
      Console keyboard events and accessibility · 41ab4396
      Samuel Thibault authored
      Some blind people use a kernel engine called Speakup which uses hardware
      synthesis to speak what gets displayed on the screen.  They use the
      PC keyboard to control this engine (start/stop, accelerate, ...) and
      also need to get keyboard feedback (to make sure to know what they are
      typing, the caps lock status, etc.)
      Up to now, the way it was done was very ugly.  Below is a patch to add a
      notifier list for permitting a far better implementation, see ChangeLog
      above for details.
      You may wonder why this can't be done at the input layer.  The problem
      is that what people want to monitor is the console keyboard, i.e. all
      input keyboards that got attached to the console, and with the currently
      active keymap (i.e. keysyms, not only keycodes).
      This adds a keyboard notifier that such modules can use to get the keyboard
      events and possibly eat them, at several stages:
      - keycodes: even before translation into keysym.
      - unbound keycodes: when no keysym is bound.
      - unicode: when the keycode would get translated into a unicode character.
      - keysym: when the keycode would get translated into a keysym.
      - post_keysym: after the keysym got interpreted, so as to see the result
        (caps lock, etc.)
      This also provides access to k_handler so as to permit simulation of
      [akpm@linux-foundation.org: various fixes]
      Signed-off-by: default avatarSamuel Thibault <samuel.thibault@ens-lyon.org>
      Cc: Jiri Kosina <jkosina@suse.cz>
      Cc: Dmitry Torokhov <dtor@mail.ru>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  6. 10 Oct, 2007 1 commit
  7. 04 Sep, 2007 1 commit
  8. 01 Apr, 2006 1 commit
  9. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      Let it rip!