Messages in this thread | | | Date | Sat, 29 May 2004 16:41:07 +0200 | From | Vojtech Pavlik <> | Subject | Re: keyboard problem with 2.6.6 |
| |
On Sat, May 29, 2004 at 04:30:43PM +0200, Andries Brouwer wrote:
> 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.
That's a good reason. I'll implement true rawmode support.
-- Vojtech Pavlik SuSE Labs, SuSE CR - 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/
| |