Re: keyboard problem with 2.6.6

From: Andries Brouwer (aebr_at_win.tue.nl)
Date: 05/29/04

  • Next message: Adrian Bunk: "Re: Recommended compiler version" 
    Date:	Sat, 29 May 2004 16:30:43 +0200
To: Vojtech Pavlik <vojtech@suse.cz>

    On Sat, May 29, 2004 at 03:46:14PM +0200, Vojtech Pavlik wrote:

    > > Thus, showkeys -s gave a garbage answer.
    > >
    > > Thanks for the report. It shows that resurrecting raw mode is even
    > > more desirable than I thought at first.
    >
    > What for?

    As you know, the keyboard/mouse situation in 2.6 is unfortunate.

    I get a steady stream with letters from people complaining about
    the keyboard utilities under 2.6. How can I answer and tell them
    what the problem is? I need facts - raw data, so that I can
    trace the path of this raw data through the kernel.

    That is my reason I want a raw mode. Often I have to ask them
    to boot 2.4 first to get reality, so that one afterwards is
    in a better position to understand the fake reality of 2.6.

    But apart from such debugging use, there is also the more
    direct use: in order to assign a keycode to an unusual key
    one first asks for the scancode using scancode -s, and then
    assigns the keycode using setkeycodes. If scancode -s lies,
    this fails.

    Andries

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Adrian Bunk: "Re: Recommended compiler version"

    Relevant Pages