summaryrefslogtreecommitdiffstats
path: root/sys/dev/hil (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Convert infinite sleeps to {m,t}sleep_nsec(9).mpi2019-12-311-2/+3
| | | | ok kn@
* Delete unnecessary <sys/file.h> includesguenther2017-12-301-2/+1
| | | | ok millert@ krw@
* Introduce a new knob to force the first USB keyboard as console input.mpi2017-03-111-2/+1
| | | | | | | By setting "machdep.forceukbd=1" you can now use your USB keyboard in ddb(4) even if your BIOS emulates a pckbd(4). ok tom@, kettenis@, deraadt@
* Use the new input functions of wsmouse in mouse and touchscreen drivers.bru2016-06-051-10/+17
| | | | ok stsp@ kettenis@
* add some missing splx() callsjsg2015-05-151-1/+2
| | | | ok deraadt@ kettenis@ krw@
* Attempt to make user changes of keyboard layout a bit more `sticky' on wsmuxmiod2014-01-261-3/+3
| | | | | | | | | | | | | | | | | kernels: - keyboard drivers will now tell wskbd if the keyboard layout they ask for is a default value, or a value they are 100% sure of (either because your kernel has a XXXKBD_LAYOUT option, or because the driver can tell the keyboard layout, e.g. by the country code on USB keyboards which provide it, such as Sun's) - when attaching a keyboard with a non-default layout, the layout will become the default layout of the mux for new keyboard attachments if the mux doesn't have a layout set already. - when changing the keyboard layout of a particular keyboard with an ioctl (i.e. using kbd(8) or wsconsctl(8)), the layout will become the default layout of the mux for new keyboard attachments. ok mpi@
* simplify kthread_create(). no more stdargderaadt2013-11-181-2/+2
| | | | ok matthew guenther mikeb
* Auto-repeat keys in WSKBD_RAW mode is not needed.shadchin2011-11-091-39/+2
| | | | | | WSKBD_RAW mode used in X, but X independently implements auto-repeat keys. ok miod@
* Missing splx() in hil_thread(). This turned out to be harmless due to themiod2010-11-201-1/+2
| | | | | way this code works (always ends up in tsleep eventually), but it never hurts to be correct.
* Replace timeout_add(msecs * hz / 1000) with timeout_add_msec(msecs).grange2009-01-211-4/+3
| | | | | | No functional changes. ok krw@ miod@
* Add support for a fourth axis on wsmouse devices, e.g. on the Apple Mightmiod2007-04-101-2/+2
| | | | | | Mouse. Currently limited to USB mice. Adapted from a diff from Gareth <garf@loveandnature.co.za> on tech@
* Button boxes have their Y axis inverted, compared to mice, so compensatemiod2006-12-161-8/+16
| | | | before feeding wscons.
* Make hil(4) shared interrupts aware, by exiting early if the stat registermiod2006-12-161-1/+10
| | | | | does not indicate data being available; for some reason on hppa hil_intr() gets invoked when serial ports interrupt.
* Handle loop reconfiguration in a kernel thread, instead of doing it frommiod2006-11-052-13/+40
| | | | interrupt context.
* Regenmiod2006-08-101-4/+4
|
* Embed device list comments in generated hildevs_data.h file; no functionalmiod2006-08-102-8/+14
| | | | change.
* Handle the ``arrow repeat'' special scancode on button boxes; from the oldmiod2006-08-102-11/+27
| | | | X11R5 server, untested.
* No need for needs-flag for hil and hilms.miod2006-08-101-4/+4
|
* Postpone the hil console detection logic to the first detection of a keyboard.miod2005-12-222-6/+19
| | | | | | | | | | | | On hp300, hil would claim console against dnkbd if no dnkbd was found at the time the loop is probed, even if the loop is empty. Because of this, plugging dnkbd later would not select it as console keyboard, which is really annoying on kernels without wsmux, such as hp300 RAMDISK. Now the first keyboard plugged will become the console keyboard, whatever its type. No functional change on hppa, since the console path gives a definite console device setting.
* Do not invoke hil_process_pendinc() from the interrupt handler if the loopmiod2005-05-131-9/+4
| | | | is marked as busy.
* Regenmiod2005-05-131-7/+7
|
* Separate button boxens from keyboards in the HIL device list.miod2005-05-134-22/+31
| | | | | hilkbd will still match both, but will neither do the auto-layout dance nor attach as console for button boxens.
* When receiving an unplugged notification from the loop, do not take actionmiod2005-05-081-15/+33
| | | | | until the loop has reconfigured into a stable state. This can save up unnecessary detach/attach cycles for the low ids in the loop.
* Simplify loop reconfiguration code.miod2005-05-081-42/+27
|
* PS/2 style and older style HIL keyboards have different layouts in theirmiod2005-05-073-151/+420
| | | | international flavours, so provide two sets of mappings.
* Regenmiod2005-05-071-2/+3
|
* KNF the output.miod2005-05-071-2/+2
|
* Fix confusion between KS_paragraph and KS_section; inspired from a PS/2miod2005-02-281-3/+3
| | | | keyboard sv map error spotted by Jan Johansson.
* WSDISPLAY_COMPAT_RAWKBD support for hilkbd.miod2005-01-183-10/+232
|
* If the loop is empty when we probe it, enable the interrupt anyways, so thatmiod2005-01-151-2/+4
| | | | we can react on post-boot device plugs.
* Reliability fixes:miod2005-01-113-12/+100
| | | | | | | - Let the loop initialize completely before attempting to probe its devices. Fixes the "no answer from device 1" problem. - Handle ``loop unplugged'' events and force detach of all children in this case.
* Allow send_hil{,dev}_cmd to return failure, and handle this wheremiod2005-01-093-30/+41
| | | | | | | | | applicable. During device probe, if a device does not answer commands, display a warning message. This apparently happens on hp300 when the console is configured as remote (i.e. serial console). Unplugging and replugging the device works fine afterwards...
* code locator is optionalmickey2004-09-151-2/+2
|
* obliterate undef, ok miodjolan2004-05-101-3/+1
|
* Hil keyboard layout for german keyboards, at least suitable for the PS/2-likemiod2004-04-061-3/+51
| | | | | | layout. Based upon an old diff from paul@, tests and feedback otto@ paul@
* Allow busy wait loops to fail, so that we don't spin if the hil loop does notmiod2004-03-121-18/+59
| | | | behave correctly for some reason.
* Relax a redundant printf format specifier.miod2003-12-201-2/+2
|
* typo from Tom Cosgrove;jmc2003-10-211-2/+2
|
* Remove the advertising clause in the UCB license which Berkeleymillert2003-06-023-18/+6
| | | | rescinded 22 July 1999. Proofed by myself and Theo.
* as mentioned in hardball ers a few delays are needed; mios@ testing on hp300 and okmickey2003-05-271-3/+12
|
* Fix various gremlins in the hilms code my simple test program did not catch,miod2003-03-281-8/+29
| | | | but XFree did.
* Better message to report an empty loop during probe.miod2003-03-281-2/+2
|
* A better explanation of why we need to operate hil keyboards in raw mode.miod2003-03-161-3/+8
|
* Better support for the ps/2-style HIL keyboards (those with a real numericmiod2003-02-262-26/+37
| | | | pad and a few extra keys).
* New hil child devices attachment framework, that allow them to be detachedmiod2003-02-266-138/+241
| | | | | | | | | | | at runtime. Handle reconfiguration notices from the loop, and do the necessary detach/attach work so that our vision of the loop is in sync with reality. Adapt all hil child devices to the above changes. "This is not as plug'n'play as usb, but you get the same feeling anyways..."
* Leaving console polling mode works now, and workaround boot -a slow responsemiod2003-02-191-5/+6
| | | | glitch.
* Oops, remove debug code that was not supposed to be left heremiod2003-02-181-6/+1
|
* Real polled mode console support, enough to play hangman in ddb.miod2003-02-183-16/+94
| | | | Still a minor issue left for tomorrow.
* Track enable state and behave appropriately.miod2003-02-181-4/+32
| | | | Also, better probe for leds on keyboard.
* A simple and crude driver to play with the hil so-called ``ID module''miod2003-02-152-1/+94
| | | | | | | | | | | | | | | | devices. The ID module only purpose is to provide a small, unique, bitstring, which was used for some copy-protection or licensing scheme under HP-UX. Right now this driver is useless, as it provides no way to communicate this information to userland, and only displays it while attaching, as such: hilid0 at hil0 code 2: ID module hilid0: security code 10 04 b4 41 ac 77 14 0f 41 00 00 00 00 00 00 00 hilid1 at hil0 code 3: ID module hilid1: security code 10 04 b4 41 e3 b8 13 0f 41 00 00 00 00 00 00 00 Too bad it's not even good enough to feed the kernel random generator...
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.