Date: Sat, 16 Nov 1996 14:09:13 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: bde@zeta.org.au (Bruce Evans) Cc: nate@freefall.freebsd.org, cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/i386/isa syscons.c syscons.h Message-ID: <199611161309.OAA07677@uriah.heep.sax.de> In-Reply-To: <199611161233.XAA17796@godzilla.zeta.org.au> from Bruce Evans at "Nov 16, 96 11:33:59 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Bruce Evans wrote: > Are there any advantages to the new mode except for easier decoding? It's not even much easier to decode. Both, mode 1 and mode 2 are really braindamaged, in that they basically emulate obsolete keyboard behaviour. Alas, the PS/2 mode 3 is not supported by all keyboards around. It's the only orthogonal mode, where each key press or release generates exactly one scan code (possibly preceded by a prefix code IIRC). No, there's not much point in having both state machines simultaneously in one driver. pcvt has a compile-time option, defaulting to ancient PC scancodes, but it only includes one state machine. I think it would even be safe to default to mode 2; i'm using this for years now. syscons' ``XT keyboard'' mode is only just another way to generate obsolete mode 1 scancodes, there are two ways to do this. (One for the keyboard, one for the controller.) Maybe i'm mistaken, and perhaps it's been as simple as syscons having relied on the BIOS to turn on the translation bit in the controller, which it apparently doesn't do on a ThinkPad. (I'm too lazy to review the code right now.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611161309.OAA07677>