merge ktrace-lwp.

branches: 1.1.4;
Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.

fix various typos in comments and log messages.

Introduce hw.alps.touchpad_movement_threshold to better button area clicks

Fix typo in sysctl node name

branches: 1.12.4;
s/recieve/receive/

Support more ALPS V2 devices

* The V2 devices found in Toshiba dynabook satellite B551/D and
dynabook SS RX1/T8E.

branches: 1.10.2;
Make the error message from pms_alps_probe_init() an error again now
that we don't misidentify almost anything as an ALPS device. Reset if
E6 check failed as well.

Don't pass response buffer to the reset command since we are not
interested in it (pckbport_poll_cmd() is smart enough).

If the first byte of E7 signature is not 0x73, it's not an ALPS
device, so don't complain we failed to initialize it. Still need a
reset, b/c the E7 check will be interpreted as normal commands by a
normal device.

When E6 signature is checked, ignore pressed buttons.

Use PMS_SEND_DEV_STATUS for E9 instead of PMS_GET_SCALE (also defined
as E9). This is more readable and is congruent with other drivers.
Same object code is generated.

Move two probe-time aprint_errors to debug and verbose level instead.

These two are regularly happening within qemu, and would muddle up the
aprint error counter otherwise.

branches: 1.4.2; 1.4.4; 1.4.6;
Remove extra newline.

If ALPS probe fails, send a PMS_RESET.
Restores functionality on a wrong version ALPS touchpad.

Addresses PR kern/52489.

This patch was prepared by/committed on behalf of maya@.

Do not print ALPS related message when generic PS/2 case

PR/52483: Ryo ONODERA: Add support for ALPS PS/2 pointing devices

s/recieve/receive/

branches: 1.1.2; 1.1.4; 1.1.8;
PR/52483: Ryo ONODERA: Add support for ALPS PS/2 pointing devices

branches: 1.1.2; 1.1.4;
PR/52483: Ryo ONODERA: Add support for ALPS PS/2 pointing devices

Ensure that the top level sysctl nodes (kern, vfs, net, ...) exist before
the sysctl link sets are processed, and remove redundancy.

Shaves >13kB off of an amd64 GENERIC, not to mention >1k duplicate
lines of code.

branches: 1.5.6; 1.5.10;
add support for elantech (v2) touchpads that report input pressure

branches: 1.4.2; 1.4.6;
Replace pms_synaptics_send_command() and identical pms_elantech_send_command()
with pms_sliced_command(). Linux shows that this sequence can also be used by
"Logitech PS/2++" protocol as well.

branches: 1.3.2; 1.3.4; 1.3.8; 1.3.10; 1.3.16;
Silence printf in common "device not found" error path.

Remove debug printfs

Add Elantech multi-touch driver.

branches: 1.1.2; 1.1.4; 1.1.8; 1.1.10; 1.1.16;
Add Elantech multi-touch driver.

add support for elantech (v2) touchpads that report input pressure

branches: 1.1.2; 1.1.4; 1.1.8; 1.1.10; 1.1.16; 1.1.24; 1.1.28;
Add Elantech multi-touch driver.

hvkbd requires pckbd_keydesctab in wskbdmap_mfii.c.

branches: 1.9.4;
PR/52483: Ryo ONODERA: Add support for ALPS PS/2 pointing devices

branches: 1.8.12; 1.8.30; 1.8.46;
options PMS_DISABLE_POWERHOOK has been obsolete for a while now,
remove what little still remains of it.

Add Elantech multi-touch driver.

branches: 1.6.6; 1.6.10; 1.6.18; 1.6.20; 1.6.26;
defflag one moe variable.

branches: 1.5.46; 1.5.52; 1.5.60;
merge ktrace-lwp.

branches: 1.4.2;
Make an new option PCKBD_CNATTACH_MAY_FAIL. When this option is set and no
keyboard is detected the pckbd keyboard is not used as the console.

Previously the pckbd keyboard was used as the console as soon as the
kernel had it configured into the kernel. This is far from ideal on a
machine that has no PS/2 keyboard, but a USB keyboard attached since the
(non-existant) PS/2 keyboard becomes the console instead of the USB keyboard.

For now this option will be off by default to be backwards compatible.

Address PR kern/28990 by making Synaptics Touchpad support contingent
on "options PMS_SYNAPTICS_TOUCHPAD" in the kernel config file. See
the PR for details on why this is necessary.

While here, defflag PMS_DISABLE_POWERHOOK.

branches: 1.2.2;
PR/28774: Kentaro A. Kurahone: Add synaptics touchpad driver

branches: 1.1.4;
Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.

fix spelling mistakes, mainly in comments and log messages.

From Vladimir 'phcoder' Serbinenko in tech-kern:

On at least some Chromebooks PS/2 reset command generates no
response and we end up reading garbage and disabling keyboard
support altogether even though that controller otherwise works
fine. Linux issues reset but ignores the reply and relies on
getid instead. So does Haiku. FreeB= SD assumes that all coreboot
systems have PS/2 which is wrong as it supports some MacBooks as
well. No idea what windows does but keyboard works there.

Also do some KNF while here.

pckbport(4): C99 initializers

No functional change intended.

Merge thorpej-cfargs2.

branches: 1.35.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

branches: 1.34.12;
pckbd_cngetc: Set type=0 and return if no data is available

branches: 1.33.6;
New device wsbell - allows for a console beep for non pckbds (usb etc).
Works for platforms without pcppi - can work with spkr at audio and spkr
at pcppi.

To use add the following to your kernel config:
wsbell* at spkr? console?

Ok pgoyette@.

Disambiguate debug message.

branches: 1.31.6;
Cosemetically "fix" the pckbd_attach() return value, so gcc can see the
value is used (no functional change)

branches: 1.30.2;
Add two flags to keyboard/mouse attachment:
PCKBC_CANT_TRANSLATE for keyboards that cannot translate to XT scancodes
PCKBC_NEED_AUXWRITE for mice that don't probe first time
These flags can be set by the port-specific attachments.

Add the translation table and function to handle set 2 to set 1 keyboard
translation in software.

Based on OpenBSD sys/dev/ic/pckbc.c revisions 1.10, 1.16, 1.17, and
sys/dev/pckbc/pckbd.c revision 1.15, and 8042 scan code information at:

http://www.computer-engineering.org/ps2keyboard/

Note, that this changes the signature of pckbc_cnattach(), so ride the
kernel version bump for namei.

branches: 1.29.10; 1.29.20;
A pointer typedef entails trading too much flexibility to declare const
and non-const types, and the kernel uses both const and non-const
PMF qualifiers and device suspensors, so change the pmf_qual_t and
device_suspensor_t typedefs from "pointers to const" to non-pointer,
non-const types.

branches: 1.28.2;
Expand PMF_FN_* macros.

Ignore scancodes E0 2A, E0 AA, E0 36, E0 B6 when decoding.
For the 10 keys on the editing keypad, these prefix/postfix
scancodes indicate the state of the Left Shift and Right Shift
keys and Num Lock indicator.

This change prevents a spurious WSCONS_EVENT_KEY_UP event upon
press as well as the corresponding WSCONS_EVENT_KEY_DOWN event
upon release.

use aprint_error

branches: 1.25.4; 1.25.6; 1.25.10; 1.25.14;
remove a KBC_ENABLE call in the console poll method -- this was
just a workaround and is not necessary anymore

branches: 1.24.2; 1.24.4;
Remove clause 3 and 4 from TNF licenses

branches: 1.23.2; 1.23.4;
Use proper types.

Split device_t and softc for pckbd(4) and pms(4).

Use PMF_FN_ARGS, PMF_FN_PROTO.

branches: 1.20.2; 1.20.6;
Ensure that the keyboard is enabled before polling it.
This allows pressing a key to reboot the machine.

Support pcppi(4) detachment.

Use device_t, device_private(). Get rid of a struct device * cast.

branches: 1.18.2;
Merge jmcneill-pm branch.

branches: 1.17.2; 1.17.4;
aprintify

branches: 1.16.2;
machine/{bus,cpu,intr}.h -> sys/{bus,cpu,intr}.h

branches: 1.15.2; 1.15.14; 1.15.16; 1.15.20;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

branches: 1.14.4;
__unused removal on arguments; approved by core.

- sprinkle __unused on function decls.
- fix a couple of unused bugs
- no more -Wno-unused for i386

Add "name" parameter to powerhook_establish, to aid debugging. No objections
on tech-kern@

branches: 1.11.4; 1.11.6;
Jared asked me to commit the powerhooks for this

branches: 1.10.2; 1.10.4;
Use device_private().

branches: 1.9.4; 1.9.6; 1.9.8; 1.9.10; 1.9.12;
merge ktrace-lwp.

branches: 1.8.2;
avoid shadowed variable

Make an new option PCKBD_CNATTACH_MAY_FAIL. When this option is set and no
keyboard is detected the pckbd keyboard is not used as the console.

Previously the pckbd keyboard was used as the console as soon as the
kernel had it configured into the kernel. This is far from ideal on a
machine that has no PS/2 keyboard, but a USB keyboard attached since the
(non-existant) PS/2 keyboard becomes the console instead of the USB keyboard.

For now this option will be off by default to be backwards compatible.

tweak order of #include to avoid an array of incomplete type.
found by gcc4.

P.k.py lp.kcrgow ao mabf ru go oycnn dak. _n.iajf_ t.fxrapeov
Allprk.e xf jrp.v

Due to the increasing rarity of legacy keyboards, switch to a more contemporary default
layout for PC style keyboards.

nuke trailing whitespace

branches: 1.2.4; 1.2.10; 1.2.12;
ANSIfy, un-__P(), and generally KNF.

Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.

From Vladimir 'phcoder' Serbinenko in tech-kern:

On at least some Chromebooks PS/2 reset command generates no
response and we end up reading garbage and disabling keyboard
support altogether even though that controller otherwise works
fine. Linux issues reset but ignores the reply and relies on
getid instead. So does Haiku. FreeB= SD assumes that all coreboot
systems have PS/2 which is wrong as it supports some MacBooks as
well. No idea what windows does but keyboard works there.

Also do some KNF while here.

Deal with Foxconn NanoPC nT-i1250 returning BAT_FAIL and don't infinite loop
From OpenBSD.

branches: 1.2.110; 1.2.120;
merge ktrace-lwp.

branches: 1.1.4;
Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.

Support pcppi(4) detachment.

Use device_t, device_private(). Get rid of a struct device * cast.

branches: 1.3.46; 1.3.52; 1.3.60;
merge ktrace-lwp.

branches: 1.2.4; 1.2.18;
ANSIfy, un-__P(), and generally KNF.

Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.

Merge thorpej-cfargs2.

branches: 1.19.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

branches: 1.18.10;
in many device attach paths, allocate memory with M_WAITOK instead of M_NOWAIT
and remove code to handle failures that can no longer happen.

branches: 1.17.30;
KASSERT that cmd is non-NULL in more places, and in a place that previously
did not use KASSERT to do the same thing.

branches: 1.16.6;
fix debugging printf

Deal with Foxconn NanoPC nT-i1250 returning BAT_FAIL and don't infinite loop
From OpenBSD.

branches: 1.14.2; 1.14.12;
const-ify input command buffer argument to
pckbport_poll_cmd and pckbport_enqueue_cmd.

Use proper types.

Split device_t and softc for pckbd(4) and pms(4).

branches: 1.11.2; 1.11.6;
Start detangling lock.h from intr.h. This is likely to cause short term
breakage, but the mess of dependencies has been regularly breaking the
build recently anyhow.

branches: 1.10.8; 1.10.14; 1.10.20;
Initialize callouts before use.

branches: 1.9.12; 1.9.14;
All ports that use the file do so through files.pckbport, so there's no
need to be cautious about including "pckbd.h". This has the side-effect
that ports using pckbd but not defining __HAVE_NWSCONS will now get pckbd
attached as console if they call pckbport_cnattach(), but I don't think
any such ports exist.

reset kbc as the comment said. from joerg.

branches: 1.7.4; 1.7.8; 1.7.14; 1.7.16;
merge ktrace-lwp.

kill a number of autoconf submatch functions which follow the
standard scheme:
if (<configured> != <wildcard> && <configured> != <real>)
then fail
else
ask device match function

This is handled by config_stdsubmatch() now.

replace the "locdesc_t" structure carrying the number of locators
explicitely by a plain integer array
the length in now known to all relevant parties, so this avoids
duplication of information, and we can allocate that thing in
drivers without hacks

branches: 1.4.12;
a round of autoconf cleanup:
-convert submatch() style functions (passed to config_search() or
config_found_sm()) to the locator passing variants
-pass interface attributes in some cases
-make submatch() functions look uniformly as far as possible
-avoid macros which just hide cfdata members, and reduce dependencies
on "locators.h"

branches: 1.3.4;
remove license clauses 3 and 4 from my cpoyright notices

ANSIfy, un-__P(), and generally KNF.

Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.

const-ify input command buffer argument to
pckbport_poll_cmd and pckbport_enqueue_cmd.

Use proper types.

Split device_t and softc for pckbd(4) and pms(4).

branches: 1.6.46; 1.6.66; 1.6.70;
merge ktrace-lwp.

branches: 1.5.2;
fix static/extern mismatch. found by gcc4.

nuke trailing whitespace

branches: 1.3.4; 1.3.10; 1.3.12;
remove license clauses 3 and 4 from my cpoyright notices

ANSIfy, un-__P(), and generally KNF.

Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.

pms: support PS/2 mouse hot-plug

Detect the BAT (Basic Assurance Test) result value and reset
the driver state in this case.

ok martin@

branches: 1.41.6;
panic on an condition that shouldn't be possible.

appease GCC 12.

pckbport(4): C99 initializers

No functional change intended.

Merge thorpej-cfargs2.

branches: 1.38.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

branches: 1.37.16;
Add comment elaborating what a sliced command is.

branches: 1.36.2; 1.36.4;
PR/52483: Ryo ONODERA: Add support for ALPS PS/2 pointing devices

branches: 1.35.12; 1.35.30;
Replace pms_synaptics_send_command() and identical pms_elantech_send_command()
with pms_sliced_command(). Linux shows that this sequence can also be used by
"Logitech PS/2++" protocol as well.

Sprinkle static.

Make whitespace more consistent.

options PMS_DISABLE_POWERHOOK has been obsolete for a while now,
remove what little still remains of it.

Use proper format string

branches: 1.30.2; 1.30.4;
A pointer typedef entails trading too much flexibility to declare const
and non-const types, and the kernel uses both const and non-const
PMF qualifiers and device suspensors, so change the pmf_qual_t and
device_suspensor_t typedefs from "pointers to const" to non-pointer,
non-const types.

branches: 1.29.2;
Expand PMF_FN_* macros.

use aprint_error

branches: 1.27.2;
Add Elantech multi-touch driver.

branches: 1.26.4; 1.26.12; 1.26.14; 1.26.20;
Use proper types.

Split device_t and softc for pckbd(4) and pms(4).

Use PMF_FN_ARGS, PMF_FN_PROTO.

branches: 1.23.2; 1.23.6;
Don't call do_enable on synaptics resume if !sc->sc_enabled

Merge jmcneill-pm branch.

branches: 1.21.2; 1.21.4;
aprintify

branches: 1.20.2;
machine/{bus,cpu,intr}.h -> sys/{bus,cpu,intr}.h

branches: 1.19.4; 1.19.6; 1.19.10; 1.19.12;
include sys/cdefs.h before opt_xxx.h

branches: 1.18.2;
Merge some of the less invasive changes from the vmlocking branch:

- kthread, callout, devsw API changes
- select()/poll() improvements
- miscellaneous MT safety improvements

branches: 1.17.2; 1.17.4;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

branches: 1.16.4;
__unused removal on arguments; approved by core.

Tidy away wsmouse_input() abstractions and update
documentation to include the W direction.

- sprinkle __unused on function decls.
- fix a couple of unused bugs
- no more -Wno-unused for i386

Add "name" parameter to powerhook_establish, to aid debugging. No objections
on tech-kern@

branches: 1.12.2;
avoid empty if bodies.

branches: 1.11.6;
merge FreeBSD timecounters from branch simonb-timecounters
- struct timeval time is gone
time.tv_sec -> time_second
- struct timeval mono_time is gone
mono_time.tv_sec -> time_uptime
- access to time via
{get,}{micro,nano,bin}time()
get* versions are fast but less precise
- support NTP nanokernel implementation (NTP API 4)
- further reading:
Timecounter Paper: http://phk.freebsd.dk/pubs/timecounter.pdf
NTP Nanokernel: http://www.eecis.udel.edu/~mills/ntp/html/kern.html

branches: 1.10.2;
Use device_private().

branches: 1.9.4; 1.9.6; 1.9.8; 1.9.10; 1.9.12;
merge ktrace-lwp.

Add a fake entry in pms_protocols array to avoid an out-of-bounds
access in do_enable() if PMS_SYNAPTICS_TOUCHPAD and PMSDEBUG are both
defined.

constify

branches: 1.6.4; 1.6.6;
nuke trailing whitespace

Fix synaptics touchpad resume, from Kentaro A. Kurahone.

branches: 1.4.2;
Address PR kern/28990 by making Synaptics Touchpad support contingent
on "options PMS_SYNAPTICS_TOUCHPAD" in the kernel config file. See
the PR for details on why this is necessary.

While here, defflag PMS_DISABLE_POWERHOOK.

branches: 1.3.2;
PR/28774: Kentaro A. Kurahone: Add synaptics touchpad driver

branches: 1.2.4;
ANSIfy, un-__P(), and generally KNF.

Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.

add PS/2 registers from synaptics spec:
PMS_RESET_WRAP_MODE, PMS_SET_WRAP_MODE, PMS_ACK, PMS_ERROR and PMS_RESEND

while here use #define<tab> consistently.

branches: 1.2.98; 1.2.104; 1.2.106;
merge ktrace-lwp.

branches: 1.1.4;
Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.

PR/52483: Ryo ONODERA: Add support for ALPS PS/2 pointing devices

branches: 1.11.12; 1.11.30;
Replace pms_synaptics_send_command() and identical pms_elantech_send_command()
with pms_sliced_command(). Linux shows that this sequence can also be used by
"Logitech PS/2++" protocol as well.

Cosmetic changes.

options PMS_DISABLE_POWERHOOK has been obsolete for a while now,
remove what little still remains of it.

Add Elantech multi-touch driver.

branches: 1.7.4; 1.7.12; 1.7.14; 1.7.20;
Use proper types.

Split device_t and softc for pckbd(4) and pms(4).

branches: 1.5.8; 1.5.24; 1.5.28;
Merge some of the less invasive changes from the vmlocking branch:

- kthread, callout, devsw API changes
- select()/poll() improvements
- miscellaneous MT safety improvements

branches: 1.4.30; 1.4.32;
merge ktrace-lwp.

branches: 1.3.4;
nuke trailing whitespace

branches: 1.2.2;
Address PR kern/28990 by making Synaptics Touchpad support contingent
on "options PMS_SYNAPTICS_TOUCHPAD" in the kernel config file. See
the PR for details on why this is necessary.

While here, defflag PMS_DISABLE_POWERHOOK.

branches: 1.1.2; 1.1.4;
PR/28774: Kentaro A. Kurahone: Add synaptics touchpad driver

hw.synaptics.aux_mid_button_scroll translates vertical movements
of an aux device (like a trackpoint) into a scroll event when
the middle mouse button is pressed.

Make this work with either the middle mouse button of the main
device (buttonmask 0x02) or the middle mouse button of the aux
device (buttonmask 0x40).

Fixes PR 58435.

branches: 1.83.2;
Renamed border/boundary variables to better describe their use.
Fix edge default values, factor out percentage calculation for more consistent
values. Use device_printf/DPRINTF to show errors instead of aprint variants.
Print raw input for debugging.

Correct capability parsing. Old devices were probed with nonexistent
commands and then used undefined boundary values that made them unusuable.

Fixes PR 57874.

panic on an condition that shouldn't be possible.

appease GCC 12.

branches: 1.81.4;
synaptics: Lower scale factor to give less sluggish mouse performance
on modern displays.

- synaptics_filter_policy no longer generates movements from stale data.
- button boundary is now computed consistently.
- multi finger operation now works for MULTI_FINGER and MULTI_FINGER_REPORT.

Fixes PR kern/56476 and probably kern/56998.

fix various typos in comments, documentation and messages.

Use the original right boundary when calculating the vertical scroll
region so the boundary does not creep left on each subsequent setting.
Thanks to Martin@ for the report.

Fix regression introduced when fixing PR kern/56613 and related tweaks

* A trackpad with external buttons needs to mask a number of lower bits
of the X and Y coordinates IFF a button is down. This was not being
done so a button held down looked like an out of range packet and
was therefore dropped.

* Now that trackpads are probed for their boundaries make the emulated
button boundary settable by a percentage, also allow the right and
bottom boundaries to be adjusted by a percentage to allow for
horizontal and vertical scroll regions.

Fix for PR kern/56613

* For trackpads that report max and min coordinates, retrieve these and
use them as the boundaries instead of the hard coded limits.
* Drop packets that are have x/y values that are outside the limits of
the trackpad. Some trackpads report a stream of low values in some
situations that cause cursor jumping.

synaptics: Fix tracking of extended buttons.

- Ensure that packets are processed whenever any button change
occurs, instead of just processing packets when there is movement
or trackpad finger activity
- Only transfer the state of the "extended buttons" to the button
masks when actual changes occur OR a button is being held down.

With this patch, my middle mouse button no longer gets "stuck down",
but proper press/release tracking and dragging behavior is preserved.

Thanks to blymn for pointers.

fix various typos in comments, log messages and documentation.

Significant update to the synaptics touchpad driver.

* Accumulate packets for primary, secondary, finger count packets
before handing off to pms_synaptics_process_packet. This means
that both primary and, possibly, secondary finger locations will
be processed at the same time. Previously the processing each
packet as it arrived.

* Fix the secondary finger position reporting, there was an off by
one in the shifts when decoding which effectively halved the
reported position.

* For a clickpad, make the emulated button region "dead" so that finger
movements in this region are ignored. This makes it easier to click
a button without accidentally repositioning the cursor. There is a
sysctl variable "button_region_movement_enable" that will allow
these finger movements to be reported if this is desirable.

* Reset the finger ballistics when the number of fingers changes. This
stops the annoying position jumps when a second finger touch is added
to or removed from the touchpad.

* Add a level argument to the DPRINTF macro so one can choose their
level of debug spam via the debug sysctl variable.

synaptics: use the new WSCONS_EVENT_(H|V)SCROLL event types
to implement two-finger scrolling. remove non-functional code for
detecting reported finger width.

synaptics(4): New sysctl knob for debug output.

Set hw.synaptics.debug=1 to re-enable it; the compile-time DIAGNOSTIC
option was inappropriate for this.

branches: 1.70.6; 1.70.8;
synaptics: Emulate scrolling when the middle button is held with TrackPoints

idea stolen from various other operating systems.

this configurable with a sysctl in case somebody wants to hold the middle
button, e.g. with old window managers that close menus when a button is
released.

erect a signpost for weary travellers

comment was likely true in 2007 but no longer reflects the reality of hw

synaptics: Don't reset the device multiple times in succession

Cherrypicked from a patch from an anonymous contributor.

pms_synaptics_enable: no need to send PMS_DEV_ENABLE here because
pms_enable does this for us. Seems to resolve issues with my trackpoint
not working immediately after starting X on ThinkPad X260.

Extended buttons are reported separate from touchpad buttons, so track
button press / release state separate from touch events.

synaptics: Maintain the left/right buttons when up/down are remapped

Reported on current-users by Mandacarú Cascavel

synaptics: Revert changes that broke gestures in cases where they worked.

It seems I have to figure out another way to make scrolling work for me.

synaptics: Increase default scale_z for more precise scrolling

synaptics: Check for single-finger event jitter in all cases.

I now have smooth two-finger scrolling.

synaptics: Detect multiple fingers outside the gesture period

I suspect this code doesn't make any sense if we want two-finger scrolling

synaptics: Automatically scroll when multiple fingers are detected

This will mean we automatically get two-finger scrolling on multitouch
pads.

This works, but the scrolling is janky. Why does it eventually move the
mouse cursor (only one finger detected, but two are still there), and why
does it jump up slightly?

synaptics: fix syntax

synaptics: Allow the max_speed sysctls to be set

synaptics: Set up_down_emulation=3 by default.

It's a less surprising default for modern hardware.

synaptics: Make up_down_emulation useful for single-button clickpads

On devices such as the Thinkpad X250, the clickpad can be pressed
to generate mouse button events 1 and 2. There are also additional
physical buttons which the pms(4) driver recognizes as "up/down" buttons
(mouse buttons 3 and 4). Allow these to be remapped to buttons 1 and 2
and used like normal touchpad buttons with the following sysctl:

# sysctl -w hw.synaptics.up_down_emulation=3

While here, adjust the existing "middle button emulation"
(hw.synaptics.up_down_emulation=1) so it works with single-button
clickpads.

XXX: 3 may be a more useful default than the current default,
depending on hardware availability of touchpads with "up/down buttons".

Update the documentation accordingly.

Messages in pms_synaptics_input() should not start with "pms_input"

Use "pms_synaptics_input" instead for another 2 messages.

Messages in pms_synaptics_input() should not start with "pms_input"

Use "pms_synaptics_input" instead.

Do not enter extended W mode conditional for non extended W mode device

Even without extended W mode, sp_w can be 2. This causes
"invalid extended w mode N" warning messages.
Restrict extended W mode conditional for hardwares with extended W
support.

Tested with Synaptics 6.2 device on Panasonic CF-Y8, however it does
not work with X.

Remove a trailing tab.

branches: 1.50.2; 1.50.4;
Resynchronizing the input stream could infinitely wait when the touchpad
is in the wrong (relative) mode. The detection of relative mode is never
reached.

Limit the resynchronization to 6 bytes, then trigger a reset.

Changes based on code from an anonymous contributor. This should make
trackpads work for Thinkpads. Also adds code to handle externally
connected buttons (synaptics parlance), the first five are mapped to
mouse buttons 1-5. The rest are currently not reported but could be
decoded if required.

Modify driver to use bits(3) to extract capabilities. Thanks to
Anon Ymous for the fix.

Fix minor comment nit.

* Increase the default scaling of the two finger scroll to make it
less sensitive
* Fix range check for hw.synaptics.scale_z so it can be set with sysctl

* Increase minimum finger width to prevent entering scroll mode erroneously
* Attempt to clarify what the sysctl variables for finger scroll do
* Add hysteresis to validity check so changing it does not get rejected

Thanks to Martin Husemann and Michael van Elst for reporting the issues.

Add double finger scroll feature. If the detected width is between a
defined range then report y movement as z-axis. Effectively emulating
a mouse scroll wheel.

Fix clamping of deltas so it works for both positive and negative deltas.

Send the 'magic reverse engineered sequence' with a single sliced command,
don't wait for individual ACKs. Fixes kern/53444.

While here:
- use better descriptive names for functions
- use a function for the extended write command
- add macro for number from the old synaptics documentation
- don't get the resp from the command sequence if we're going to ignore
it anyway

most from uwe.

branches: 1.41.2;
restore \n printing.

use a more data-driven :-) approach to avoid cut-n-pasted code.

Enable Synaptics multifinger capability (Extended W mode)

Magic parameters are taken from
https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller/.
Tested on HP ProBook 4630s, Lenovo E530, VAIO Pro 11 and HP Spectre x360 ae.

Remove double and trailing whitespaces

Remove trailing tab

branches: 1.36.2;
Add hw.synaptics.movement_enable sysctl. Default value is 1, but if set
to 0 disables movement events from the touchpad.

While here, fixup a few sysctl nodenum comparisons in
pms_sysctl_synaptics_verify to compare against node numbers instead of
values.

Return res in non-synaptics case like before. Fix ALPS case

Add two finger support and middle/right button emulation.

Fix clickpad button detection (From Rhialto)

branches: 1.32.2; 1.32.4;
PR/48831: J�rg Grundmann: Synaptics Touch pad (ClickPad) and
Klick-by-tap-gestures do not work

branches: 1.31.2;
Ensure that the top level sysctl nodes (kern, vfs, net, ...) exist before
the sysctl link sets are processed, and remove redundancy.

Shaves >13kB off of an amd64 GENERIC, not to mention >1k duplicate
lines of code.

branches: 1.30.2; 1.30.4;
Remove a couple of (void *) casts added in the previous commin.
They aren't needed here (script error).

Add some pre-processor magic to verify that the type of the data item
passed to sysctl_createv() actually matches the declared type for
the item itself.
In the places where the caller specifies a function and a structure
address (typically the 'softc') an explicit (void *) cast is now needed.
Fixes bugs in sys/dev/acpi/asus_acpi.c sys/dev/bluetooth/bcsp.c
sys/kern/vfs_bio.c sys/miscfs/syncfs/sync_subr.c and setting
AcpiGbl_EnableAmlDebugObject.
(mostly passing the address of a uint64_t when typed as CTLTYPE_INT).
I've test built quite a few kernels, but there may be some unfixed MD
fallout. Most likely passing &char[] to char *.
Also add CTLFLAG_UNSIGNED for unsiged decimals - not set yet.

branches: 1.28.2;
Correct and improve some comments. Collect unused variables. Add a define.

Replace pms_synaptics_send_command() and identical pms_elantech_send_command()
with pms_sliced_command(). Linux shows that this sequence can also be used by
"Logitech PS/2++" protocol as well.

use aprint_debug_dev and get rid of SYNAPTICSDEBUG

branches: 1.25.2; 1.25.4;
wakeup needs sys/proc.h.

send the SET_SCALE11 command before the 'sliced' command as per the
Linux driver (and elantech(4)), via PR kern/42853

Extended capability probes can confuse the passthrough device,
reset the touchpad on enable to cure that.

some definitions from the Linux driver (via PR kern/42853)

branches: 1.21.10; 1.21.20; 1.21.22;
Make various bits of debug code compile again.

branches: 1.20.2; 1.20.4;
Split device_t and softc for pckbd(4) and pms(4).

branches: 1.19.2; 1.19.6;
Change synaptics 'unusual delay' printf to aprint_debug. I'm tired of
seeing it over and over again.

De-noisify resume handler.

use __KERNEL_RCSID()

branches: 1.16.2; 1.16.4; 1.16.6; 1.16.8;
machine/{bus,cpu,intr}.h -> sys/{bus,cpu,intr}.h

branches: 1.15.8; 1.15.10; 1.15.14;
add missing W coordinate

Handle events from passthrough devices like the Thinkpad 'Navistick'.

branches: 1.13.2; 1.13.4; 1.13.8; 1.13.10; 1.13.12;
__unused removal on arguments; approved by core.

Tidy away wsmouse_input() abstractions and update
documentation to include the W direction.

- sprinkle __unused on function decls.
- fix a couple of unused bugs
- no more -Wno-unused for i386

branches: 1.10.6; 1.10.8;
merge FreeBSD timecounters from branch simonb-timecounters
- struct timeval time is gone
time.tv_sec -> time_second
- struct timeval mono_time is gone
mono_time.tv_sec -> time_uptime
- access to time via
{get,}{micro,nano,bin}time()
get* versions are fast but less precise
- support NTP nanokernel implementation (NTP API 4)
- further reading:
Timecounter Paper: http://phk.freebsd.dk/pubs/timecounter.pdf
NTP Nanokernel: http://www.eecis.udel.edu/~mills/ntp/html/kern.html

branches: 1.9.4; 1.9.6; 1.9.8; 1.9.14;
Remove leading __ from __(const|inline|signed|volatile) -- it is obsolete.

merge ktrace-lwp.

s/SYNAPTICS_DEBUG/SYNAPTICSDEBUG/ to keep consistency.

branches: 1.6.2; 1.6.4;
Change the rest of the sysctl subsystem to use const consistently.
The __UNCONST macro is now used only where necessary and the RW macros
are gone. Most of the changes here are consumers of the
sysctl_createv(9) interface that now takes a pair of const pointers
which used not to be.

nuke trailing whitespace

branches: 1.4.2;
Address PR kern/28990 by making Synaptics Touchpad support contingent
on "options PMS_SYNAPTICS_TOUCHPAD" in the kernel config file. See
the PR for details on why this is necessary.

While here, defflag PMS_DISABLE_POWERHOOK.

branches: 1.3.2; 1.3.4;
Major re-write of the recently-committed Synaptics Touchpad driver,
prompted by jittery and/or random movement during tap gestures, lack
of edge motion, and a general desire to make use of the extra features
available with the native protocol.

- Ditch the kernel thread; it was overkill for the small amount of
processing required to deal with touchpad events.

- If we fail to probe a Synaptics touchpad, issue a RESET command
to ensure that whatever device is out there is left in a sane
state (thanks to Reinoud Zandijk for the hint).

- Completely re-write gesture support.

- Put the touchpad in 80 packets per second mode and count them so
they can be used to time gesture durations (instead of using
mono_time).

- Enhance up/down button support with options to use them to emulate
the middle button or Z-axis events (like a traditional wheel mouse).

- Add 'edge motion'. If a drag gesture is in progress, and the reported
finger position moves to the touchpad's border region, continue
to report movement events at a fixed rate as if the finger carried
on moving in the same direction. This restores some functionality
usually provided by the touchpad's firmware in PS/2 mode.

- Filter successive movement events to reduce jitter. When scaling
movement events, fold the remainder into the next event to prevent
loss of information during slow/small finger movements. Pointer
movement is now much more refined.

- Add support for touchpads which can report more than one finger on
the pad simultaneously. Optionally use this feature for middle/right
button emulation (i.e. tap two fingers to emulate middle button).
This feature is disabled by default (for now) to avoid surprise
pasting of clipboard text. ;-)

- cleanup some debugging stuff.
- don't create the sysctl nodes if we don't have a synaptics pad.

PR/28774: Kentaro A. Kurahone: Add synaptics touchpad driver

Define 'query resolution' command and submodel capability field.

branches: 1.13.10;

Fix for PR kern/56613

* For trackpads that report max and min coordinates, retrieve these and
use them as the boundaries instead of the hard coded limits.
* Drop packets that are have x/y values that are outside the limits of
the trackpad. Some trackpads report a stream of low values in some
situations that cause cursor jumping.

Changes based on code from an anonymous contributor. This should make
trackpads work for Thinkpads. Also adds code to handle externally
connected buttons (synaptics parlance), the first five are mapped to
mouse buttons 1-5. The rest are currently not reported but could be
decoded if required.

Modify driver to use bits(3) to extract capabilities. Thanks to
Anon Ymous for the fix.

Send the 'magic reverse engineered sequence' with a single sliced command,
don't wait for individual ACKs. Fixes kern/53444.

While here:
- use better descriptive names for functions
- use a function for the extended write command
- add macro for number from the old synaptics documentation
- don't get the resp from the command sequence if we're going to ignore
it anyway

most from uwe.

branches: 1.9.2; 1.9.4;
Add two finger support and middle/right button emulation.

PR/48831: J�rg Grundmann: Synaptics Touch pad (ClickPad) and
Klick-by-tap-gestures do not work

branches: 1.7.12; 1.7.26;
Correct and improve some comments. Collect unused variables. Add a define.

some definitions from the Linux driver (via PR kern/42853)

branches: 1.5.44; 1.5.56; 1.5.66; 1.5.68;
Don't call queries "PS/2 commands", it's confusing.
Add queries to read mode and model id (not used yet).
Fix SYNAPTICS_CAP_EXTNUM - it's 3 bits [14:12], not 2.

branches: 1.4.20;
merge ktrace-lwp.

branches: 1.3.4;
nuke trailing whitespace

branches: 1.2.2; 1.2.4; 1.2.6;
Major re-write of the recently-committed Synaptics Touchpad driver,
prompted by jittery and/or random movement during tap gestures, lack
of edge motion, and a general desire to make use of the extra features
available with the native protocol.

- Ditch the kernel thread; it was overkill for the small amount of
processing required to deal with touchpad events.

- If we fail to probe a Synaptics touchpad, issue a RESET command
to ensure that whatever device is out there is left in a sane
state (thanks to Reinoud Zandijk for the hint).

- Completely re-write gesture support.

- Put the touchpad in 80 packets per second mode and count them so
they can be used to time gesture durations (instead of using
mono_time).

- Enhance up/down button support with options to use them to emulate
the middle button or Z-axis events (like a traditional wheel mouse).

- Add 'edge motion'. If a drag gesture is in progress, and the reported
finger position moves to the touchpad's border region, continue
to report movement events at a fixed rate as if the finger carried
on moving in the same direction. This restores some functionality
usually provided by the touchpad's firmware in PS/2 mode.

- Filter successive movement events to reduce jitter. When scaling
movement events, fold the remainder into the next event to prevent
loss of information during slow/small finger movements. Pointer
movement is now much more refined.

- Add support for touchpads which can report more than one finger on
the pad simultaneously. Optionally use this feature for middle/right
button emulation (i.e. tap two fingers to emulate middle button).
This feature is disabled by default (for now) to avoid surprise
pasting of clipboard text. ;-)

PR/28774: Kentaro A. Kurahone: Add synaptics touchpad driver

Fix regression introduced when fixing PR kern/56613 and related tweaks

* A trackpad with external buttons needs to mask a number of lower bits
of the X and Y coordinates IFF a button is down. This was not being
done so a button held down looked like an out of range packet and
was therefore dropped.

* Now that trackpads are probed for their boundaries make the emulated
button boundary settable by a percentage, also allow the right and
bottom boundaries to be adjusted by a percentage to allow for
horizontal and vertical scroll regions.

Fix for PR kern/56613

* For trackpads that report max and min coordinates, retrieve these and
use them as the boundaries instead of the hard coded limits.
* Drop packets that are have x/y values that are outside the limits of
the trackpad. Some trackpads report a stream of low values in some
situations that cause cursor jumping.

Significant update to the synaptics touchpad driver.

* Accumulate packets for primary, secondary, finger count packets
before handing off to pms_synaptics_process_packet. This means
that both primary and, possibly, secondary finger locations will
be processed at the same time. Previously the processing each
packet as it arrived.

* Fix the secondary finger position reporting, there was an off by
one in the shifts when decoding which effectively halved the
reported position.

* For a clickpad, make the emulated button region "dead" so that finger
movements in this region are ignored. This makes it easier to click
a button without accidentally repositioning the cursor. There is a
sysctl variable "button_region_movement_enable" that will allow
these finger movements to be reported if this is desirable.

* Reset the finger ballistics when the number of fingers changes. This
stops the annoying position jumps when a second finger touch is added
to or removed from the touchpad.

* Add a level argument to the DPRINTF macro so one can choose their
level of debug spam via the debug sysctl variable.

Fix hardcoded size for total_patckets array in synaptics_softc, it
needs to be SYN_MAX_FINGERS because the driver expects it to be.

branches: 1.10.6;
Extended buttons are reported separate from touchpad buttons, so track
button press / release state separate from touch events.

branches: 1.9.2;
Changes based on code from an anonymous contributor. This should make
trackpads work for Thinkpads. Also adds code to handle externally
connected buttons (synaptics parlance), the first five are mapped to
mouse buttons 1-5. The rest are currently not reported but could be
decoded if required.

Add double finger scroll feature. If the detected width is between a
defined range then report y movement as z-axis. Effectively emulating
a mouse scroll wheel.

branches: 1.7.2; 1.7.4;
Add two finger support and middle/right button emulation.

PR/48831: J�rg Grundmann: Synaptics Touch pad (ClickPad) and
Klick-by-tap-gestures do not work

branches: 1.5.12; 1.5.26;
Correct and improve some comments. Collect unused variables. Add a define.

merge ktrace-lwp.

nuke trailing whitespace

branches: 1.2.2; 1.2.4; 1.2.6;
Major re-write of the recently-committed Synaptics Touchpad driver,
prompted by jittery and/or random movement during tap gestures, lack
of edge motion, and a general desire to make use of the extra features
available with the native protocol.

- Ditch the kernel thread; it was overkill for the small amount of
processing required to deal with touchpad events.

- If we fail to probe a Synaptics touchpad, issue a RESET command
to ensure that whatever device is out there is left in a sane
state (thanks to Reinoud Zandijk for the hint).

- Completely re-write gesture support.

- Put the touchpad in 80 packets per second mode and count them so
they can be used to time gesture durations (instead of using
mono_time).

- Enhance up/down button support with options to use them to emulate
the middle button or Z-axis events (like a traditional wheel mouse).

- Add 'edge motion'. If a drag gesture is in progress, and the reported
finger position moves to the touchpad's border region, continue
to report movement events at a fixed rate as if the finger carried
on moving in the same direction. This restores some functionality
usually provided by the touchpad's firmware in PS/2 mode.

- Filter successive movement events to reduce jitter. When scaling
movement events, fold the remainder into the next event to prevent
loss of information during slow/small finger movements. Pointer
movement is now much more refined.

- Add support for touchpads which can report more than one finger on
the pad simultaneously. Optionally use this feature for middle/right
button emulation (i.e. tap two fingers to emulate middle button).
This feature is disabled by default (for now) to avoid surprise
pasting of clipboard text. ;-)

PR/28774: Kentaro A. Kurahone: Add synaptics touchpad driver

wskbd(4): Define USB and PS/2 keymaps for KB_PL

This is the de-facto standard "Polish programmers" QWERTY keyboard,
what X11 simply calls "Polish". It's a simple variation of US QWERTY
with some extra characters when right alt is pressed.

Defining this layout is slightly optimistic, since even with latin-2
fonts loaded and the appropriate locale set, wscons seems to struggle
to input most of these characters.

Regardless, this allows the supposedly supported "pl" encoding
to not fail loading with an error message, and allows X11 to
auto-detect the keyboard layout (defining KB_PL and as an alias of
KB_US also accomplishes this goal), with room for proper UTF-8
support in the future.

PR port-amd64/57234 "# wsconsctl -k -w encoding=pl" *should* work.
PR kern/57844 wscons doesn't support encoding=pl contrary to wskbd(4) man page
PR install/58405 Selecting Polish keyboard type in sysinst is useless

branches: 1.35.4; 1.35.10;
wscons: add definitions for BÉPO, a standardized, Dvorak-style optimized
keyboard layout for French

wscons: add support for the Neo 2 German keyboard layout

Neo is an optimized layout for German and English, similar to
Dvorak for English. It can be used to type most Latin-based languages
and has separate layers for symbols and directional commands.

branches: 1.33.6; 1.33.8;
Canadian French keyboard layout for ukbd/pckbd

Add keyboard layout for Latin American Spanish to ukbd/pckbd

Add Icelandic keyboard layout to ukbd/pckbd.

Add Estonian layout as a variation of Swedish for ukbd and pckbd

Bring br.nodead closer to X11

Add support for the Brazilian keyboard layout to pckbd and ukbd.

This is significantly different from the European Portugese layout,
and was pieced together from Wikipedia, X11 layout files, and to
some extent with trial and error.

Thanks to lun-4 for helping test this.

PR kern/44570

Support the combination of KB_SWAPCTRLCAPS and UK layout.

branches: 1.26.4; 1.26.10; 1.26.12;
Add Turkish keyboard layout.

from berte in PR kern/53011.

branches: 1.25.20;
Add a belgian keyboard layout, based on the french keyboard layout.
Fixes PR install/46871.

Nuke trailing whitespace.

branches: 1.23.10;
Add the extra keys found on the Tadpole SPARCle to the keysym list.

branches: 1.22.2; 1.22.8; 1.22.12;
fixes from gilbert dot fernandes at orange dot fr

fixes from OpenBSD

PR/35473: Wigcher Spanninga: Add Dutch keyboard support to wscons

Add hungarian qwertz keyboard layout.

Add support for Swiss german kezboard to wskbd.

Contributed by Marc Balmer.

Add a Czech (QWERTY) keyboard layout, and teach wscons about latin 2 characters.

Original code from Lubomir Kundrak, adapted to current and cleaned up by me.

Fixes PR kern/16216

ok agc@ jdc@

branches: 1.16.2;
Enable Colemak altgr keys.

branches: 1.15.6; 1.15.8;
Add support for the Colemak keyboard layout variant, see http://colemak.com

branches: 1.14.2;
Remove clause 3 and 4 from TNF licenses

branches: 1.13.6; 1.13.8; 1.13.10;
defflag one moe variable.

branches: 1.12.2;
Merge jmcneill-pm branch.

branches: 1.11.12; 1.11.26; 1.11.32; 1.11.34; 1.11.40; 1.11.44; 1.11.46;
Greek console keymap from Eye of the Beholder

branches: 1.10.4; 1.10.6; 1.10.8; 1.10.10; 1.10.12;
merge ktrace-lwp.

branches: 1.9.2;
Fix for portuguese keymap '4' and '+' keys, from Rui Paulo

Fix for Portuguese keymap from Rui Paulo

branches: 1.7.2;
nuke trailing whitespace

branches: 1.6.2; 1.6.4;
Add KB_ES | KB_MACHDEP placeholder for Jornada 680/690 Spanish (ABE).

Add & document WSKBD_USONLY: In order to strip down the space usage of wscons,
all keymaps except the US english one can be removed from the kernel
with this option, which results in a space gain of about 10kB.

XXX it would be nice if we could strip down more kernel facilities

Allow keypad PgUp/PgDn to scroll as well.

by popular demand, bind the scroll keys by default.

branches: 1.2.2; 1.2.4;
Add KB_FR | KB_MACHDEP placeholder. Need it for the Jornada 680/690
French (ABF) keyboard layout (to be enabled soon).

Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.

Remove clause 3 and 4 from TNF licenses

branches: 1.2.70; 1.2.72; 1.2.74;
merge ktrace-lwp.

branches: 1.1.4;
Abstract the interface between pckbc(4), and the pckbd(4) and pms(4)
drivers that attach to it. This allows for other host interface chips
that use the same keyboards and mice, such as the ones in the ARM
IOMD20, ARM7500, and SA-1111. The PC-compatible driver is still
called pckbc(4), and the new abstraction layer is "pckbport", so the
child devices have moved from sys/dev/pckbc to sys/dev/pckbport, which
also contains some code shared between all host controllers. To avoid
incompatibility, pckbdreg.h is still installed in
/usr/include/dev/pckbc.

In theory, this shouldn't cause any behavioural changes in the drivers
concerned. Thy just use rather more function pointers than before. Tested
on i386 and (with a new host driver) acorn32. Compiled on several other
affected architectures.