From owner-freebsd-current Tue Nov 19 01:17:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA24623 for current-outgoing; Tue, 19 Nov 1996 01:17:29 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA24616 for ; Tue, 19 Nov 1996 01:17:14 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA19159 for ; Tue, 19 Nov 1996 10:16:33 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA25697 for freebsd-current@FreeBSD.org; Tue, 19 Nov 1996 10:16:32 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id KAA07256 for freebsd-current@FreeBSD.org; Tue, 19 Nov 1996 10:05:24 +0100 (MET) From: J Wunsch Message-Id: <199611190905.KAA07256@uriah.heep.sax.de> Subject: Re: UserConfig is broken + PS/2 support success To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 19 Nov 1996 10:05:24 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611190600.PAA03041@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Nov 19, 96 03:00:29 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Kazutaka YOKOTA wrote: I've ignored the beginning of this discussion. > bit 6 0 No conversion of keyboard scan codes. > 1 Standard Scan conversion - the scan code from the keyboard is > converted into the normal scan codes used in PCs (1 is normal > operation). MCA Type 2 controllers cannot set this bit to 1. > In this case scan code conversion is set using keyboard > command F0h to port 60h. Right. The latter is why syscons didn't work out of the box on ThinkPads. > addition, the AT keyboard can send three different sets of scan codes: > > set 1 XT scan code set > set 2 AT scan code set (default) > set 3 for manufacturing test? No, the AT keyboard (84-key one, almost forgotten now) has only 1 and 2. Set 3 is only applicable to PS/2-style keyboards. Alas, not all keyboards around are PS/2-style, even not in these days. So while set 3 is the most orthogonal one (the only one that doesn't generate compatibility cruft like all the crap you get in set 2 when pressing Alt SysRq or Ctrl PrtScr), we cannot rely on it. > So, I think we can have the following hardware combinations to get > XT scan codes: > > 1. XT keyboard with an ISA/EISA style keyboard controller No, i don't think we really support XT keyboards, and probably nobody really wants this either. Our world starts with an AT design (e.g. we also rely on having an RTC available), and we can ignore the XT part. Older keyboards (like mine -- 1990 manufactured) still have an XT/AT switch somewhere, but they won't work in XT mode with messy DOS on the AT-style machine either. So simply don't worry about this case. -- 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. ;-)