Messages in this thread | | | Subject | Re: keyboard problem with 2.6.6 | From | Sau Dan Lee <> | Date | 30 May 2004 15:25:10 +0200 |
| |
>>>>> "Vojtech" == Vojtech Pavlik <vojtech@suse.cz> writes:
>> How about the PS/2 mouse port? It's not just for mice. There >> ARE implementations using it for other things: touchpad, >> touchscreen, etc.
Vojtech> All simulate a mouse.
Yeah. All can fall back to PS/2 mouse emulation mode. But to enable the extended features, you need to write to the port to enable them, and then interpret the extended data formats.
Vojtech> No. I'm just saying - if you want something that's not in Vojtech> the kernel drivers, just write a driver for it. But the Vojtech> driver must be able to coexist with the other drivers.
It's easier to write a mouse driver in userspace than in kernel. But with the input system in 2.6, I am *forced* to write it in kernel space, and reboot and reboot and reboot when it oops. Writing the driver in kernel space, I at most get a segfault. Plus I cannot use everything from glibc. It simply takes more time and energy to write a kernel space driver.
Vojtech> Your psaux/userspace serio driver is fine, except it Vojtech> cannot coexist with the other drivers.
That's why I've abandoned it. It's obsolete.
Our (Tuukka and I) SERIO_USERDEV patch does work with kernel drivers, and allow both kernel and userland drivers to coexist. Again, I'm disappointed that you still haven't discovered this.
Now, it's time for you to try our SERIO_USERDEV patch, plus my crude userspace atkbd.c and psmouse drivers.
Vojtech> Anyway, at least 99% setups just keep working in 2.6.
But not 100% compatibly. Mouse moving twice as fast, mouse not accelerating, etc. And tp4d not working any more. And touch screen not working. ...
Vojtech> The raw data not what you want to use there. You want the Vojtech> keystroke data, >> No. I want the raw bytes. (That's also useful for debugging >> a hardware, in case people are making or experimenting with new >> hardware.)
Vojtech> Sure. For debugging purposes, yes. But for analyzing the Vojtech> typing behavior, the abstract data is better.
It depends on what level I want to analyze at. How come you have a crystal ball telling you that you know what I want?
>> I could study the I-Ching in English, but I would prefer to do >> it in Chinese. Now, your approach is forcing me to do it in >> English. And you believe that's a good idea.
Vojtech> In your example, you wanted to study the frequency of Vojtech> keypresses, and their relations. For that, it's best to Vojtech> ask the kernel to report keypresses to you.
No. The kernel has already translated the data.
-- Sau Dan LEE 李守敦(Big5) ~{@nJX6X~}(HZ)
E-mail: danlee@informatik.uni-freiburg.de Home page: http://www.informatik.uni-freiburg.de/~danlee
- 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/
| |