Eric Lee / smarc-fsl-linux-kernel

02 Nov, 2017

1 commit

  • b24413180   License cleanup: add SPDX GPL-2.0 license identifier to files with no license ... Browse Code »

    Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license of the kernel, which is GPL version 2.

    Update the files which contain no license information with the 'GPL-2.0'
    SPDX license identifier. The SPDX identifier is a legally binding
    shorthand, which can be used instead of the full boiler plate text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart and
    Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset of
    the use cases:
    - file had no licensing information it it.
    - file was a */uapi/* one with no licensing information in it,
    - file was a */uapi/* one with existing licensing information,

    Further patches will be generated in subsequent months to fix up cases
    where non-standard license headers were used, and references to license
    had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied to
    a file was done in a spreadsheet of side by side results from of the
    output of two independent scanners (ScanCode & Windriver) producing SPDX
    tag:value files created by Philippe Ombredanne. Philippe prepared the
    base worksheet, and did an initial spot review of a few 1000 files.

    The 4.13 kernel was the starting point of the analysis with 60,537 files
    assessed. Kate Stewart did a file by file comparison of the scanner
    results in the spreadsheet to determine which SPDX license identifier(s)
    to be applied to the file. She confirmed any determination that was not
    immediately clear with lawyers working with the Linux Foundation.

    Criteria used to select files for SPDX license identifier tagging was:
    - Files considered eligible had to be source code files.
    - Make and config files were included as candidates if they contained >5
    lines of source
    - File already had some variant of a license header in it (even if
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

13 Oct, 2012

1 commit

09 Mar, 2012

1 commit

  • 079c9534a   vt:tackle kbd_table ... Browse Code »
    43

    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: Alan Cox
    Signed-off-by: Greg Kroah-Hartman

    Alan Cox
     

15 Jun, 2009

1 commit

  • 5a7e3d128   keyboard: advertise KT_DEAD2 extended diacriticals ... Browse Code »

    In addition to KT_DEAD which has limited support for diacriticals,
    there is KT_DEAD2 that can support 256 criticals, so let's advertise
    it in .

    This lets userland know abut the drivers/char/keyboard.c function
    k_dead2, which supports more than the few trivial ones that k_dead
    supports.

    Signed-off-by: Samuel Thibault
    Signed-off-by: Linus Torvalds

    Samuel Thibault
     

15 Apr, 2008

1 commit

20 Oct, 2007

1 commit

  • 41ab4396e   Console keyboard events and accessibility ... Browse Code »

    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
    keypresses.

    [akpm@linux-foundation.org: various fixes]
    Signed-off-by: Samuel Thibault
    Cc: Jiri Kosina
    Cc: Dmitry Torokhov
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Samuel Thibault
     

13 Oct, 2007

1 commit

11 Oct, 2007

1 commit

05 Sep, 2007

1 commit

02 Apr, 2006

1 commit

  • b9ec4e109   Input: add support for Braille devices ... Browse Code »

    - Add KEY_BRL_* input keys and K_BRL_* keycodes;
    - Add emulation of how braille keyboards usually combine braille dots
    to the console keyboard driver;
    - Add handling of unicode U+28xy diacritics.

    Signed-off-by: Samuel Thibault
    Signed-off-by: Dmitry Torokhov

    Samuel Thibault
     

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    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!

    Linus Torvalds