summaryrefslogtreecommitdiffstats
path: root/sys/isa/kbdio.c
Commit message (Collapse)AuthorAgeFilesLines
* Don't (conditionally) override the kernel's min() and max() functionsbde1998-02-131-7/+4
| | | | | | | with macros. This breaks if the functions are replaced by macros with unsuitable semantics. Define a MAX() macro unconditionally instead. max() is unsuitable since we need a constant expression. Don't define MIN() - we never used min().
* Removed unused #includes.bde1997-07-201-7/+1
|
* Made set_controller_command_byte() less verbose. It used to print ayokota1997-03-071-6/+2
| | | | | | | debug message whenever one of lock keys were pressed, if the system was started with the `-v' option. Removed a couple of lines of dead code too.
* Move pcvt towards using kbdio (finally!).joerg1997-03-061-2/+3
| | | | | | | | | | Warning: this won't work yet with PCVT_SCANSET=2 along in early console mode (boot -c, or boot -d). A big thanks to Kazutaka, and a word of apologies for delaying the review for that long time... Submitted by: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA)
* Back out part 1 of the MCFH that changed $Id$ to $FreeBSD$. We are notpeter1997-02-221-1/+1
| | | | ready for it yet.
* Fix for the Compaq Armada laptop.yokota1997-02-071-3/+9
| | | | | | | | | | The PS/2 mouse device responds to a reset command with a sequence of ACK(fa), RESULT(aa) and ID(00). Most PS/2 mice immediately returns ACK, but spend sometime before sending RESULT. The Armada takes time before ACK; extra delay is necessary before the call to read ACK. The problem was reported in comp.unix.bsd.freebsd.misc and the patch was tested by the reporter. No PR was filed, by the way.
* - Modified for PC-98.kato1997-01-161-5/+34
| | | | - Included IBM-PC specific code in #ifndef PC98.
* Upgrade the kbdio rutines to provide queued kbd & mouse events.sos1997-01-151-156/+639
| | | | | | Minor other updates to syscons by me. Submitted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* Synchronize with the RELENG_2_2 branch.asami1996-12-041-12/+26
| | | | | | Definite 2.2 candidate. Submitted by: The FreeBSD(98) Development Team
* Alot of fixes from kazu:sos1996-12-011-104/+151
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. All the suggestions earlier made by Bruce: renaming some symbols, stricter error checking, removing redundant code, etc. 2. The `psm' driver preserves the default counter resolution and report rate, whatever they are after reset. (Based on reports and suggestion from Nate and Rob Bolin). 3. The `psm' driver now does not check the so-called sync. bit in the first byte of the data packet by default, so that the tapping feature of ALPUS GlidePoint works (based on reports from Louis Mamakos). I tested the code with ALPUS Desktop GlidePoint (M/N GP101) and found no problem; tapping worked. It appears ALPUS produces several models of GlidePoint. I hope the other models are OK too. The check code can still be activated by defining the PSM_CHECKSYNC option in the config file. (The bit checking slightly reduces, if not completely eliminates, weird mouse behavior cased by unsynchronized mouse data packets. It also helps us to detect if the mouse interrupt can ever be lost. But, well, if there are devices which cannot be supported this way...) 4. The `psm' driver does not include the protocol emulation code by default. The code can still be compiled in if the PSM_EMULATION option is specified in the config file. Louis Mamakos suggests the emulation code is putting too much in the kernel, and `moused' works well. I will think about this later and decide if the entire emulation code should be removed. 5. And, of course, the fix in `scprobe()' from Bruce to cure the UserConfig problem. My code in `kbdio.c' is slightly different from his patch, but has the same effect. There still is a possibility that `scprobe()' gets confused, if, for whatever reasons, the user holds down a key for very long time during the boot process. But we cannot cope with everything, can we? Submitted by: Kazutaka YOKOTA (yokota@zodiac.mech.utsunomiya-u.ac.jp)
* Finally a start at sharing the kdb controller routines betweensos1996-11-141-0/+470
syscons and psm, curtesy Kazutaka Yokota with minor changes by me. This contains an update of the psm driver as well. This also fixes the breakage that I introduced to the psm driver by making syscons poll for keyboard events in the atempt to fix the hanging keyboard problem. It works perfectly for me, and I'd like to hear from all that have had keyboard/ps/2 mouse problems if this is the cure... Submitted by: Kazutaka YOKOTA (yokota@zodiac.mech.utsunomiya-u.ac.jp)
OpenPOWER on IntegriCloud