Re: Keyboard and Mouse library

[linuxassembly@evobsyniva.com]

On Wed, 16 Jul 2003 07:46:30 +0100, hp <lx@lxhp.in-berlin.de> wrote:

> linuxassembly@evobsyniva.com am Mittwoch, 16. Juli 2003 04:09:
>> On Wed, 16 Jul 2003 03:03:15 -0700, jeff <jko@save-net.com> wrote:
>>
>> There are some mysterious ioctls that control this as well, but they 
>> don't
>> seem to be documented anywhere at all.  However, you can simply call the
>
> man 4 console_ioctl (or console_ioctls, old vers.)

The only thing I see that might apply is KDGKBENT and KDSKBSENT.  They 
might be related, but I can't tell, and suspect they are not.  There's no 
mention of anything that might remove the line buffering, or the byte 3 
leading to a sigkill thing.  As I mentioned, setting the keyboard in raw 
mode doesn't remove these things, it just mucks them up.  Instead of 
control-C sending a sigkill, it becomes the number 2 key, who's scan code 
is 3.

Doing an strace on stty reveals that it calls two mystery ioctls 0x5401 and 
0x5403, and looking around the kernel source I figured out they are TCGETS 
and TCSETSW, however I've been unsuccessful in tracking down any more 
information than that.  The two ioctls lead to drivers/char/tty_ioctl.c, 
which calls a function set_termios, which calls change_termios, which calls 
???.set_termios, and that's about where my ability to read C code comes to 
an end.