The 8042 emulation found on Chromebooks does not support the RESET command,
for no good reason, and causes pckbc not to attach. However, sending a `get
keyboard id' works, so this can be used as a second check to give those
fawlty pieces of hardware a chance to work.

Based on a diff submitted by, and tested by, Vladimir 'phcoder' Serbinenko.

Extend the PCKBC_CANT_TRANSLATE feature, specific to Tadpole/RDI hardware,
to also support scan code set #3 in addition to the existing scan code set #2.

This makes the built-in keyboard on the Tadpole UltraBook IIe work.

Use RAWKEY constants for scan code tables, rather than magic numbers.
No functional change intended.

Delete obsolete /* ARGSUSED */ lint comments.

ok miod@ millert@

constify struct cfattach

spelling
feedback and ok tb@ jmc@ ok ratchov@

Do not overwrite `table' in the non-translating case.

This ensures the keyboard is using the expected scancode.

From miod@, problem also noticed by Markus Hennecke, ok otto@

pckbd: don't change translation mode if controller is in table 2

This was changed a decade ago to forcibly try table 3 first in order
to make some now-long-gone hardware work.

Newer Lenovo machines seem to have trouble being asked to change
modes which manifests as a long boot delay as it waits for each
request to timeout, or by causing the keyboard to generate junk when
typing.

Assume table 2 by default and just leave it alone if it's already
there. This is how Linux has operated for quite a while and seems
to help on these Lenovo machines.

Tested by a few with these machines and has been in snaps for a bit.

Re-enable pckbd on resume (similar to what we do on boot). Fixes problems
on (at least) various HP laptops that previously had no working keyboard
after resuming from 'zzz'.

Reported by Aleksandar Lakic, who also verified several versions of the
diff during development, thanks.

discussed with miod and kettenis, tested by many others on tech@ - thanks.

Print irq informations in pckbc_set_inputhandler().

ok miod@

Revert 1.39. Resetting after specifically putting the keyboard in a
different table will most likely just revert the keyboard to its
default table anyway.

Instead, just flush the kbd slot before choosing a table and then
still forcefully enable the slot, which is enough to fix UKC on the
3rd gen X1 carbon while having a much smaller chance of breaking
anything else.

ok deraadt

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@

On first cnpoll, reset the keyboard and pms hard. This is required
to make "boot -c" support work on a variety of newer machines.
Do not anticipate this harming older machines, but we'll have to wait
and see with this change in the tree.
with jcs

Speed up the boot sequence by deferring the scan of xt keyboard code set.

If you were wondering why there's a pause of 5 seconds after loading the
kernel and before seeing the copyright in blue when booting some of your
machines, well this is for you!

mlarkin@ found that this delay is caused by some code probing for xt scan
code tables when pckbd(4) initialize the console keyboard. So this diff
implements an idea from deraadt@ to only do the scan once, either during
*attach() or if we enter ddb> or ukc> before that!

ok miod@, mlarkin@, deraadt@, shadchin@

my bad, last commit was not ok deraadt, revert it.

Don't use volume keys when in raw-mode (this doesn't work), and let
Xorg driver do the translation and handle them as regular keys. Fixes
confusion caused by the volume being changed twice in contradictory
ways: once by X programs and once by the pckbd(4) driver.

ok deraadt, kettenis

Attempt to make user changes of keyboard layout a bit more `sticky' on wsmux
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@

backout latest: audio keys can autorepeat. Autorepeated keys are not
decoded by the wskbd layer, thus autorepeted audio keys end-up passed
to userland in raw mode (ie to X), resulting in keyboard input
corruption. Noticed (and debugged) by halex@, thanks.

don't propagate XF86XK_Audio{Lower,Raise}Volume keys to userspace,
otherwise volume may be adjusted twice: once by X apps and once in
the kernel.

feedback from many, ok shadchin@

simplify pckbc_xt_translation()
* call only for set translation on (once in /sys/dev/pckbd.c)
therefore we can delete unused code.
* change behavior (more standard) - return zero on success

ok miod@

Ansify non-ansified function definitions. No functional change.

ok miod@

small cleanup ioctl WSKBDIO_GETLEDS

ok miod@

removed slot argument of function pckbd_cnattach
because it is always PCKBC_KBD_SLOT

ok miod@, krw@

In pckbd_scancode_translate(), correctly translate the break sequence
between scan code sets 1 and 2.

Don't do anything on suspend/resume for now (there is a diff brewing,
but it has some problems still..)

Disable the heuristics for legacy free systems if pckbc flags are set to 1
in UKC; found the hard way by jakemsr@ on an old Tecra laptop.

For DVACT_SUSPEND and DVACT_RESUME we should always return success.

pckbd_activate() should return failure if it knows; ok pirofti

better style is DVACT_SUSPEND before DVACT_RESUME

Fix pckbd and acpihpet suspend/resume cases to fit with the future framework
that's going to get in really soon.

Okay mlarkin@, deraadt@.

Get rid of devact enum, substitute it with an int and coresponding defines.

This is needed for the addition of further suspend/resume actions.

Okay deraadt@, marco@.

Legacy-free PC hardware do not have a real PS/2 keyboard controller, but
rather have the USB HCI emulate it during boot, while legacy mode is enabled.

This causes pckbd0 to attach as the console device, but is lost as soon as
the USB HCI driver attaches.

The disappearance of the emulated PS/2 controller can however be detected
in pckbc(4) - which is supposed to attach after [eou]hci(4), with the controller
refusing to ack commands and replying ``please resend'' instead.

In that case, the kernel will now no longer attach pckbd, and will perform a
new console input device selection, allowing the (real) usb keyboard to
become the console.

Thanks to krw@ for countless tests on legacy-free hardware; also tested on
more conventional hardware by naddy@ and I.

Only amd64 and i386 platforms are affected by this change.

Forgot to add break to the switch cases. Silly.
Okay deraadt@.

Add wake/suspend support for pckbd(4).

Patch initially from mlarkin@. KNF and refactoring by me.
Suggestions and okay deraadt@.

Make sure pckbd_scancode_translate() returns a scancode with the break/release
bit set if needed, in all cases. This fixes rawkbd operation on controllers
which require the kernel to perform scancode translation.

Found by and ok kettenis@

Move #include <dev/pckbc/wskbdmap_mfii.h> after including
dev/wscons/wsksymvar.h where struct wskbd_mapdata gets
declared.

ok miod@

If pckbc_xt_translation() fails, do not try to force the keyboard in table
1; instead, try table 2 first, then 1: some older keyboards, connected to
a castrated 8042, do not know how to talk in table 1 (or worse, will report
they do while they don't).

If automatic translation is not possible, remember which table the keyboard
ended configured in, and convert the scancodes from table 2 to table 1 if
necessary.

ok kettenis@

First pass at removing clauses 3 and 4 from NetBSD licenses.

Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.

OK deraadt@

Keep running the scancode translation state machine even when the keyboard
is set to raw mode, but only feed decoded events to wscons if non-raw mode.

Then, as an exception to this, pass the audio control keys events to
wscons even if in raw mode, so that the in-kernel mixer control code can
perform its work. The event is also seen by the raw event consumer (i.e.
the X server).

Requested and tested by many...

miod says noone needs isa/isavar.h anymore, and i believe him

use NULL to point to the response buffer, which avoids confusion; ok fgsch

- Remove a shadow declaration.
- Correct resp size.

deraadt@ ok.

default to have pckbd_set_xtscancode() instruct the 8042 to use
table 3, still falling back on table 2 or 1 after carefully checking
that the table set request took

fixes the keyboard on the oqo model 01/01+

in snaps for a while, tested by many

ok miod@

go via pckbc_enqeue_cmd() in pckbd_enable() if on; fixes PR 4615

ok miod@, mickey@

send enable cmd after a reset; form netbsd

typos from Tom Cosgrove;

Remove the advertising clause in the UCB license which Berkeley
rescinded 22 July 1999. Proofed by myself and Theo.

First round of __P removal in sys

Don't include isavar.h on sparc64

branches: 1.2.4; 1.2.8;
Remove dead code.

Machine-independent PC-like keyboard driver; from NetBSD. XXX - Not used
anywhere quite yet, but useful to have these files in the tree while we work
towards wscons for i386 and alpha.

Extend the PCKBC_CANT_TRANSLATE feature, specific to Tadpole/RDI hardware,
to also support scan code set #3 in addition to the existing scan code set #2.

This makes the built-in keyboard on the Tadpole UltraBook IIe work.

Use RAWKEY constants for scan code tables, rather than magic numbers.
No functional change intended.

Delete obsolete /* ARGSUSED */ lint comments.

ok miod@ millert@

constify struct cfattach

spelling
feedback and ok tb@ jmc@ ok ratchov@

Do not overwrite `table' in the non-translating case.

This ensures the keyboard is using the expected scancode.

From miod@, problem also noticed by Markus Hennecke, ok otto@

pckbd: don't change translation mode if controller is in table 2

This was changed a decade ago to forcibly try table 3 first in order
to make some now-long-gone hardware work.

Newer Lenovo machines seem to have trouble being asked to change
modes which manifests as a long boot delay as it waits for each
request to timeout, or by causing the keyboard to generate junk when
typing.

Assume table 2 by default and just leave it alone if it's already
there. This is how Linux has operated for quite a while and seems
to help on these Lenovo machines.

Tested by a few with these machines and has been in snaps for a bit.

Re-enable pckbd on resume (similar to what we do on boot). Fixes problems
on (at least) various HP laptops that previously had no working keyboard
after resuming from 'zzz'.

Reported by Aleksandar Lakic, who also verified several versions of the
diff during development, thanks.

discussed with miod and kettenis, tested by many others on tech@ - thanks.

Print irq informations in pckbc_set_inputhandler().

ok miod@

Revert 1.39. Resetting after specifically putting the keyboard in a
different table will most likely just revert the keyboard to its
default table anyway.

Instead, just flush the kbd slot before choosing a table and then
still forcefully enable the slot, which is enough to fix UKC on the
3rd gen X1 carbon while having a much smaller chance of breaking
anything else.

ok deraadt

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@

On first cnpoll, reset the keyboard and pms hard. This is required
to make "boot -c" support work on a variety of newer machines.
Do not anticipate this harming older machines, but we'll have to wait
and see with this change in the tree.
with jcs

Speed up the boot sequence by deferring the scan of xt keyboard code set.

If you were wondering why there's a pause of 5 seconds after loading the
kernel and before seeing the copyright in blue when booting some of your
machines, well this is for you!

mlarkin@ found that this delay is caused by some code probing for xt scan
code tables when pckbd(4) initialize the console keyboard. So this diff
implements an idea from deraadt@ to only do the scan once, either during
*attach() or if we enter ddb> or ukc> before that!

ok miod@, mlarkin@, deraadt@, shadchin@

my bad, last commit was not ok deraadt, revert it.

Don't use volume keys when in raw-mode (this doesn't work), and let
Xorg driver do the translation and handle them as regular keys. Fixes
confusion caused by the volume being changed twice in contradictory
ways: once by X programs and once by the pckbd(4) driver.

ok deraadt, kettenis

Attempt to make user changes of keyboard layout a bit more `sticky' on wsmux
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@

backout latest: audio keys can autorepeat. Autorepeated keys are not
decoded by the wskbd layer, thus autorepeted audio keys end-up passed
to userland in raw mode (ie to X), resulting in keyboard input
corruption. Noticed (and debugged) by halex@, thanks.

don't propagate XF86XK_Audio{Lower,Raise}Volume keys to userspace,
otherwise volume may be adjusted twice: once by X apps and once in
the kernel.

feedback from many, ok shadchin@

simplify pckbc_xt_translation()
* call only for set translation on (once in /sys/dev/pckbd.c)
therefore we can delete unused code.
* change behavior (more standard) - return zero on success

ok miod@

Ansify non-ansified function definitions. No functional change.

ok miod@

small cleanup ioctl WSKBDIO_GETLEDS

ok miod@

removed slot argument of function pckbd_cnattach
because it is always PCKBC_KBD_SLOT

ok miod@, krw@

In pckbd_scancode_translate(), correctly translate the break sequence
between scan code sets 1 and 2.

Don't do anything on suspend/resume for now (there is a diff brewing,
but it has some problems still..)

Disable the heuristics for legacy free systems if pckbc flags are set to 1
in UKC; found the hard way by jakemsr@ on an old Tecra laptop.

For DVACT_SUSPEND and DVACT_RESUME we should always return success.

pckbd_activate() should return failure if it knows; ok pirofti

better style is DVACT_SUSPEND before DVACT_RESUME

Fix pckbd and acpihpet suspend/resume cases to fit with the future framework
that's going to get in really soon.

Okay mlarkin@, deraadt@.

Get rid of devact enum, substitute it with an int and coresponding defines.

This is needed for the addition of further suspend/resume actions.

Okay deraadt@, marco@.

Legacy-free PC hardware do not have a real PS/2 keyboard controller, but
rather have the USB HCI emulate it during boot, while legacy mode is enabled.

This causes pckbd0 to attach as the console device, but is lost as soon as
the USB HCI driver attaches.

The disappearance of the emulated PS/2 controller can however be detected
in pckbc(4) - which is supposed to attach after [eou]hci(4), with the controller
refusing to ack commands and replying ``please resend'' instead.

In that case, the kernel will now no longer attach pckbd, and will perform a
new console input device selection, allowing the (real) usb keyboard to
become the console.

Thanks to krw@ for countless tests on legacy-free hardware; also tested on
more conventional hardware by naddy@ and I.

Only amd64 and i386 platforms are affected by this change.

Forgot to add break to the switch cases. Silly.
Okay deraadt@.

Add wake/suspend support for pckbd(4).

Patch initially from mlarkin@. KNF and refactoring by me.
Suggestions and okay deraadt@.

Make sure pckbd_scancode_translate() returns a scancode with the break/release
bit set if needed, in all cases. This fixes rawkbd operation on controllers
which require the kernel to perform scancode translation.

Found by and ok kettenis@

Move #include <dev/pckbc/wskbdmap_mfii.h> after including
dev/wscons/wsksymvar.h where struct wskbd_mapdata gets
declared.

ok miod@

If pckbc_xt_translation() fails, do not try to force the keyboard in table
1; instead, try table 2 first, then 1: some older keyboards, connected to
a castrated 8042, do not know how to talk in table 1 (or worse, will report
they do while they don't).

If automatic translation is not possible, remember which table the keyboard
ended configured in, and convert the scancodes from table 2 to table 1 if
necessary.

ok kettenis@

First pass at removing clauses 3 and 4 from NetBSD licenses.

Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.

OK deraadt@

Keep running the scancode translation state machine even when the keyboard
is set to raw mode, but only feed decoded events to wscons if non-raw mode.

Then, as an exception to this, pass the audio control keys events to
wscons even if in raw mode, so that the in-kernel mixer control code can
perform its work. The event is also seen by the raw event consumer (i.e.
the X server).

Requested and tested by many...

miod says noone needs isa/isavar.h anymore, and i believe him

use NULL to point to the response buffer, which avoids confusion; ok fgsch

- Remove a shadow declaration.
- Correct resp size.

deraadt@ ok.

default to have pckbd_set_xtscancode() instruct the 8042 to use
table 3, still falling back on table 2 or 1 after carefully checking
that the table set request took

fixes the keyboard on the oqo model 01/01+

in snaps for a while, tested by many

ok miod@

go via pckbc_enqeue_cmd() in pckbd_enable() if on; fixes PR 4615

ok miod@, mickey@

send enable cmd after a reset; form netbsd

typos from Tom Cosgrove;

Remove the advertising clause in the UCB license which Berkeley
rescinded 22 July 1999. Proofed by myself and Theo.

First round of __P removal in sys

Don't include isavar.h on sparc64

branches: 1.2.4; 1.2.8;
Remove dead code.

Machine-independent PC-like keyboard driver; from NetBSD. XXX - Not used
anywhere quite yet, but useful to have these files in the tree while we work
towards wscons for i386 and alpha.

Delete obsolete /* ARGSUSED */ lint comments.

ok miod@ millert@

constify struct cfattach

spelling
feedback and ok tb@ jmc@ ok ratchov@

Do not overwrite `table' in the non-translating case.

This ensures the keyboard is using the expected scancode.

From miod@, problem also noticed by Markus Hennecke, ok otto@

pckbd: don't change translation mode if controller is in table 2

This was changed a decade ago to forcibly try table 3 first in order
to make some now-long-gone hardware work.

Newer Lenovo machines seem to have trouble being asked to change
modes which manifests as a long boot delay as it waits for each
request to timeout, or by causing the keyboard to generate junk when
typing.

Assume table 2 by default and just leave it alone if it's already
there. This is how Linux has operated for quite a while and seems
to help on these Lenovo machines.

Tested by a few with these machines and has been in snaps for a bit.

Re-enable pckbd on resume (similar to what we do on boot). Fixes problems
on (at least) various HP laptops that previously had no working keyboard
after resuming from 'zzz'.

Reported by Aleksandar Lakic, who also verified several versions of the
diff during development, thanks.

discussed with miod and kettenis, tested by many others on tech@ - thanks.

Print irq informations in pckbc_set_inputhandler().

ok miod@

Revert 1.39. Resetting after specifically putting the keyboard in a
different table will most likely just revert the keyboard to its
default table anyway.

Instead, just flush the kbd slot before choosing a table and then
still forcefully enable the slot, which is enough to fix UKC on the
3rd gen X1 carbon while having a much smaller chance of breaking
anything else.

ok deraadt

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@

On first cnpoll, reset the keyboard and pms hard. This is required
to make "boot -c" support work on a variety of newer machines.
Do not anticipate this harming older machines, but we'll have to wait
and see with this change in the tree.
with jcs

Speed up the boot sequence by deferring the scan of xt keyboard code set.

If you were wondering why there's a pause of 5 seconds after loading the
kernel and before seeing the copyright in blue when booting some of your
machines, well this is for you!

mlarkin@ found that this delay is caused by some code probing for xt scan
code tables when pckbd(4) initialize the console keyboard. So this diff
implements an idea from deraadt@ to only do the scan once, either during
*attach() or if we enter ddb> or ukc> before that!

ok miod@, mlarkin@, deraadt@, shadchin@

my bad, last commit was not ok deraadt, revert it.

Don't use volume keys when in raw-mode (this doesn't work), and let
Xorg driver do the translation and handle them as regular keys. Fixes
confusion caused by the volume being changed twice in contradictory
ways: once by X programs and once by the pckbd(4) driver.

ok deraadt, kettenis

Attempt to make user changes of keyboard layout a bit more `sticky' on wsmux
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@

backout latest: audio keys can autorepeat. Autorepeated keys are not
decoded by the wskbd layer, thus autorepeted audio keys end-up passed
to userland in raw mode (ie to X), resulting in keyboard input
corruption. Noticed (and debugged) by halex@, thanks.

don't propagate XF86XK_Audio{Lower,Raise}Volume keys to userspace,
otherwise volume may be adjusted twice: once by X apps and once in
the kernel.

feedback from many, ok shadchin@

simplify pckbc_xt_translation()
* call only for set translation on (once in /sys/dev/pckbd.c)
therefore we can delete unused code.
* change behavior (more standard) - return zero on success

ok miod@

Ansify non-ansified function definitions. No functional change.

ok miod@

small cleanup ioctl WSKBDIO_GETLEDS

ok miod@

removed slot argument of function pckbd_cnattach
because it is always PCKBC_KBD_SLOT

ok miod@, krw@

In pckbd_scancode_translate(), correctly translate the break sequence
between scan code sets 1 and 2.

Don't do anything on suspend/resume for now (there is a diff brewing,
but it has some problems still..)

Disable the heuristics for legacy free systems if pckbc flags are set to 1
in UKC; found the hard way by jakemsr@ on an old Tecra laptop.

For DVACT_SUSPEND and DVACT_RESUME we should always return success.

pckbd_activate() should return failure if it knows; ok pirofti

better style is DVACT_SUSPEND before DVACT_RESUME

Fix pckbd and acpihpet suspend/resume cases to fit with the future framework
that's going to get in really soon.

Okay mlarkin@, deraadt@.

Get rid of devact enum, substitute it with an int and coresponding defines.

This is needed for the addition of further suspend/resume actions.

Okay deraadt@, marco@.

Legacy-free PC hardware do not have a real PS/2 keyboard controller, but
rather have the USB HCI emulate it during boot, while legacy mode is enabled.

This causes pckbd0 to attach as the console device, but is lost as soon as
the USB HCI driver attaches.

The disappearance of the emulated PS/2 controller can however be detected
in pckbc(4) - which is supposed to attach after [eou]hci(4), with the controller
refusing to ack commands and replying ``please resend'' instead.

In that case, the kernel will now no longer attach pckbd, and will perform a
new console input device selection, allowing the (real) usb keyboard to
become the console.

Thanks to krw@ for countless tests on legacy-free hardware; also tested on
more conventional hardware by naddy@ and I.

Only amd64 and i386 platforms are affected by this change.

Forgot to add break to the switch cases. Silly.
Okay deraadt@.

Add wake/suspend support for pckbd(4).

Patch initially from mlarkin@. KNF and refactoring by me.
Suggestions and okay deraadt@.

Make sure pckbd_scancode_translate() returns a scancode with the break/release
bit set if needed, in all cases. This fixes rawkbd operation on controllers
which require the kernel to perform scancode translation.

Found by and ok kettenis@

Move #include <dev/pckbc/wskbdmap_mfii.h> after including
dev/wscons/wsksymvar.h where struct wskbd_mapdata gets
declared.

ok miod@

If pckbc_xt_translation() fails, do not try to force the keyboard in table
1; instead, try table 2 first, then 1: some older keyboards, connected to
a castrated 8042, do not know how to talk in table 1 (or worse, will report
they do while they don't).

If automatic translation is not possible, remember which table the keyboard
ended configured in, and convert the scancodes from table 2 to table 1 if
necessary.

ok kettenis@

First pass at removing clauses 3 and 4 from NetBSD licenses.

Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.

OK deraadt@

Keep running the scancode translation state machine even when the keyboard
is set to raw mode, but only feed decoded events to wscons if non-raw mode.

Then, as an exception to this, pass the audio control keys events to
wscons even if in raw mode, so that the in-kernel mixer control code can
perform its work. The event is also seen by the raw event consumer (i.e.
the X server).

Requested and tested by many...

miod says noone needs isa/isavar.h anymore, and i believe him

use NULL to point to the response buffer, which avoids confusion; ok fgsch

- Remove a shadow declaration.
- Correct resp size.

deraadt@ ok.

default to have pckbd_set_xtscancode() instruct the 8042 to use
table 3, still falling back on table 2 or 1 after carefully checking
that the table set request took

fixes the keyboard on the oqo model 01/01+

in snaps for a while, tested by many

ok miod@

go via pckbc_enqeue_cmd() in pckbd_enable() if on; fixes PR 4615

ok miod@, mickey@

send enable cmd after a reset; form netbsd

typos from Tom Cosgrove;

Remove the advertising clause in the UCB license which Berkeley
rescinded 22 July 1999. Proofed by myself and Theo.

First round of __P removal in sys

Don't include isavar.h on sparc64

branches: 1.2.4; 1.2.8;
Remove dead code.

Machine-independent PC-like keyboard driver; from NetBSD. XXX - Not used
anywhere quite yet, but useful to have these files in the tree while we work
towards wscons for i386 and alpha.

constify struct cfattach

spelling
feedback and ok tb@ jmc@ ok ratchov@

Do not overwrite `table' in the non-translating case.

This ensures the keyboard is using the expected scancode.

From miod@, problem also noticed by Markus Hennecke, ok otto@

pckbd: don't change translation mode if controller is in table 2

This was changed a decade ago to forcibly try table 3 first in order
to make some now-long-gone hardware work.

Newer Lenovo machines seem to have trouble being asked to change
modes which manifests as a long boot delay as it waits for each
request to timeout, or by causing the keyboard to generate junk when
typing.

Assume table 2 by default and just leave it alone if it's already
there. This is how Linux has operated for quite a while and seems
to help on these Lenovo machines.

Tested by a few with these machines and has been in snaps for a bit.

Re-enable pckbd on resume (similar to what we do on boot). Fixes problems
on (at least) various HP laptops that previously had no working keyboard
after resuming from 'zzz'.

Reported by Aleksandar Lakic, who also verified several versions of the
diff during development, thanks.

discussed with miod and kettenis, tested by many others on tech@ - thanks.

Print irq informations in pckbc_set_inputhandler().

ok miod@

Revert 1.39. Resetting after specifically putting the keyboard in a
different table will most likely just revert the keyboard to its
default table anyway.

Instead, just flush the kbd slot before choosing a table and then
still forcefully enable the slot, which is enough to fix UKC on the
3rd gen X1 carbon while having a much smaller chance of breaking
anything else.

ok deraadt

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@

On first cnpoll, reset the keyboard and pms hard. This is required
to make "boot -c" support work on a variety of newer machines.
Do not anticipate this harming older machines, but we'll have to wait
and see with this change in the tree.
with jcs

Speed up the boot sequence by deferring the scan of xt keyboard code set.

If you were wondering why there's a pause of 5 seconds after loading the
kernel and before seeing the copyright in blue when booting some of your
machines, well this is for you!

mlarkin@ found that this delay is caused by some code probing for xt scan
code tables when pckbd(4) initialize the console keyboard. So this diff
implements an idea from deraadt@ to only do the scan once, either during
*attach() or if we enter ddb> or ukc> before that!

ok miod@, mlarkin@, deraadt@, shadchin@

my bad, last commit was not ok deraadt, revert it.

Don't use volume keys when in raw-mode (this doesn't work), and let
Xorg driver do the translation and handle them as regular keys. Fixes
confusion caused by the volume being changed twice in contradictory
ways: once by X programs and once by the pckbd(4) driver.

ok deraadt, kettenis

Attempt to make user changes of keyboard layout a bit more `sticky' on wsmux
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@

backout latest: audio keys can autorepeat. Autorepeated keys are not
decoded by the wskbd layer, thus autorepeted audio keys end-up passed
to userland in raw mode (ie to X), resulting in keyboard input
corruption. Noticed (and debugged) by halex@, thanks.

don't propagate XF86XK_Audio{Lower,Raise}Volume keys to userspace,
otherwise volume may be adjusted twice: once by X apps and once in
the kernel.

feedback from many, ok shadchin@

simplify pckbc_xt_translation()
* call only for set translation on (once in /sys/dev/pckbd.c)
therefore we can delete unused code.
* change behavior (more standard) - return zero on success

ok miod@

Ansify non-ansified function definitions. No functional change.

ok miod@

small cleanup ioctl WSKBDIO_GETLEDS

ok miod@

removed slot argument of function pckbd_cnattach
because it is always PCKBC_KBD_SLOT

ok miod@, krw@

In pckbd_scancode_translate(), correctly translate the break sequence
between scan code sets 1 and 2.

Don't do anything on suspend/resume for now (there is a diff brewing,
but it has some problems still..)

Disable the heuristics for legacy free systems if pckbc flags are set to 1
in UKC; found the hard way by jakemsr@ on an old Tecra laptop.

For DVACT_SUSPEND and DVACT_RESUME we should always return success.

pckbd_activate() should return failure if it knows; ok pirofti

better style is DVACT_SUSPEND before DVACT_RESUME

Fix pckbd and acpihpet suspend/resume cases to fit with the future framework
that's going to get in really soon.

Okay mlarkin@, deraadt@.

Get rid of devact enum, substitute it with an int and coresponding defines.

This is needed for the addition of further suspend/resume actions.

Okay deraadt@, marco@.

Legacy-free PC hardware do not have a real PS/2 keyboard controller, but
rather have the USB HCI emulate it during boot, while legacy mode is enabled.

This causes pckbd0 to attach as the console device, but is lost as soon as
the USB HCI driver attaches.

The disappearance of the emulated PS/2 controller can however be detected
in pckbc(4) - which is supposed to attach after [eou]hci(4), with the controller
refusing to ack commands and replying ``please resend'' instead.

In that case, the kernel will now no longer attach pckbd, and will perform a
new console input device selection, allowing the (real) usb keyboard to
become the console.

Thanks to krw@ for countless tests on legacy-free hardware; also tested on
more conventional hardware by naddy@ and I.

Only amd64 and i386 platforms are affected by this change.

Forgot to add break to the switch cases. Silly.
Okay deraadt@.

Add wake/suspend support for pckbd(4).

Patch initially from mlarkin@. KNF and refactoring by me.
Suggestions and okay deraadt@.

Make sure pckbd_scancode_translate() returns a scancode with the break/release
bit set if needed, in all cases. This fixes rawkbd operation on controllers
which require the kernel to perform scancode translation.

Found by and ok kettenis@

Move #include <dev/pckbc/wskbdmap_mfii.h> after including
dev/wscons/wsksymvar.h where struct wskbd_mapdata gets
declared.

ok miod@

If pckbc_xt_translation() fails, do not try to force the keyboard in table
1; instead, try table 2 first, then 1: some older keyboards, connected to
a castrated 8042, do not know how to talk in table 1 (or worse, will report
they do while they don't).

If automatic translation is not possible, remember which table the keyboard
ended configured in, and convert the scancodes from table 2 to table 1 if
necessary.

ok kettenis@

First pass at removing clauses 3 and 4 from NetBSD licenses.

Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.

OK deraadt@

Keep running the scancode translation state machine even when the keyboard
is set to raw mode, but only feed decoded events to wscons if non-raw mode.

Then, as an exception to this, pass the audio control keys events to
wscons even if in raw mode, so that the in-kernel mixer control code can
perform its work. The event is also seen by the raw event consumer (i.e.
the X server).

Requested and tested by many...

miod says noone needs isa/isavar.h anymore, and i believe him

use NULL to point to the response buffer, which avoids confusion; ok fgsch

- Remove a shadow declaration.
- Correct resp size.

deraadt@ ok.

default to have pckbd_set_xtscancode() instruct the 8042 to use
table 3, still falling back on table 2 or 1 after carefully checking
that the table set request took

fixes the keyboard on the oqo model 01/01+

in snaps for a while, tested by many

ok miod@

go via pckbc_enqeue_cmd() in pckbd_enable() if on; fixes PR 4615

ok miod@, mickey@

send enable cmd after a reset; form netbsd

typos from Tom Cosgrove;

Remove the advertising clause in the UCB license which Berkeley
rescinded 22 July 1999. Proofed by myself and Theo.

First round of __P removal in sys

Don't include isavar.h on sparc64

branches: 1.2.4; 1.2.8;
Remove dead code.

Machine-independent PC-like keyboard driver; from NetBSD. XXX - Not used
anywhere quite yet, but useful to have these files in the tree while we work
towards wscons for i386 and alpha.

spelling
feedback and ok tb@ jmc@ ok ratchov@

Do not overwrite `table' in the non-translating case.

This ensures the keyboard is using the expected scancode.

From miod@, problem also noticed by Markus Hennecke, ok otto@

pckbd: don't change translation mode if controller is in table 2

This was changed a decade ago to forcibly try table 3 first in order
to make some now-long-gone hardware work.

Newer Lenovo machines seem to have trouble being asked to change
modes which manifests as a long boot delay as it waits for each
request to timeout, or by causing the keyboard to generate junk when
typing.

Assume table 2 by default and just leave it alone if it's already
there. This is how Linux has operated for quite a while and seems
to help on these Lenovo machines.

Tested by a few with these machines and has been in snaps for a bit.

Re-enable pckbd on resume (similar to what we do on boot). Fixes problems
on (at least) various HP laptops that previously had no working keyboard
after resuming from 'zzz'.

Reported by Aleksandar Lakic, who also verified several versions of the
diff during development, thanks.

discussed with miod and kettenis, tested by many others on tech@ - thanks.

Print irq informations in pckbc_set_inputhandler().

ok miod@

Revert 1.39. Resetting after specifically putting the keyboard in a
different table will most likely just revert the keyboard to its
default table anyway.

Instead, just flush the kbd slot before choosing a table and then
still forcefully enable the slot, which is enough to fix UKC on the
3rd gen X1 carbon while having a much smaller chance of breaking
anything else.

ok deraadt

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@

On first cnpoll, reset the keyboard and pms hard. This is required
to make "boot -c" support work on a variety of newer machines.
Do not anticipate this harming older machines, but we'll have to wait
and see with this change in the tree.
with jcs

Speed up the boot sequence by deferring the scan of xt keyboard code set.

If you were wondering why there's a pause of 5 seconds after loading the
kernel and before seeing the copyright in blue when booting some of your
machines, well this is for you!

mlarkin@ found that this delay is caused by some code probing for xt scan
code tables when pckbd(4) initialize the console keyboard. So this diff
implements an idea from deraadt@ to only do the scan once, either during
*attach() or if we enter ddb> or ukc> before that!

ok miod@, mlarkin@, deraadt@, shadchin@

my bad, last commit was not ok deraadt, revert it.

Don't use volume keys when in raw-mode (this doesn't work), and let
Xorg driver do the translation and handle them as regular keys. Fixes
confusion caused by the volume being changed twice in contradictory
ways: once by X programs and once by the pckbd(4) driver.

ok deraadt, kettenis

Attempt to make user changes of keyboard layout a bit more `sticky' on wsmux
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@

backout latest: audio keys can autorepeat. Autorepeated keys are not
decoded by the wskbd layer, thus autorepeted audio keys end-up passed
to userland in raw mode (ie to X), resulting in keyboard input
corruption. Noticed (and debugged) by halex@, thanks.

don't propagate XF86XK_Audio{Lower,Raise}Volume keys to userspace,
otherwise volume may be adjusted twice: once by X apps and once in
the kernel.

feedback from many, ok shadchin@

simplify pckbc_xt_translation()
* call only for set translation on (once in /sys/dev/pckbd.c)
therefore we can delete unused code.
* change behavior (more standard) - return zero on success

ok miod@

Ansify non-ansified function definitions. No functional change.

ok miod@

small cleanup ioctl WSKBDIO_GETLEDS

ok miod@

removed slot argument of function pckbd_cnattach
because it is always PCKBC_KBD_SLOT

ok miod@, krw@

In pckbd_scancode_translate(), correctly translate the break sequence
between scan code sets 1 and 2.

Don't do anything on suspend/resume for now (there is a diff brewing,
but it has some problems still..)

Disable the heuristics for legacy free systems if pckbc flags are set to 1
in UKC; found the hard way by jakemsr@ on an old Tecra laptop.

For DVACT_SUSPEND and DVACT_RESUME we should always return success.

pckbd_activate() should return failure if it knows; ok pirofti

better style is DVACT_SUSPEND before DVACT_RESUME

Fix pckbd and acpihpet suspend/resume cases to fit with the future framework
that's going to get in really soon.

Okay mlarkin@, deraadt@.

Get rid of devact enum, substitute it with an int and coresponding defines.

This is needed for the addition of further suspend/resume actions.

Okay deraadt@, marco@.

Legacy-free PC hardware do not have a real PS/2 keyboard controller, but
rather have the USB HCI emulate it during boot, while legacy mode is enabled.

This causes pckbd0 to attach as the console device, but is lost as soon as
the USB HCI driver attaches.

The disappearance of the emulated PS/2 controller can however be detected
in pckbc(4) - which is supposed to attach after [eou]hci(4), with the controller
refusing to ack commands and replying ``please resend'' instead.

In that case, the kernel will now no longer attach pckbd, and will perform a
new console input device selection, allowing the (real) usb keyboard to
become the console.

Thanks to krw@ for countless tests on legacy-free hardware; also tested on
more conventional hardware by naddy@ and I.

Only amd64 and i386 platforms are affected by this change.

Forgot to add break to the switch cases. Silly.
Okay deraadt@.

Add wake/suspend support for pckbd(4).

Patch initially from mlarkin@. KNF and refactoring by me.
Suggestions and okay deraadt@.

Make sure pckbd_scancode_translate() returns a scancode with the break/release
bit set if needed, in all cases. This fixes rawkbd operation on controllers
which require the kernel to perform scancode translation.

Found by and ok kettenis@

Move #include <dev/pckbc/wskbdmap_mfii.h> after including
dev/wscons/wsksymvar.h where struct wskbd_mapdata gets
declared.

ok miod@

If pckbc_xt_translation() fails, do not try to force the keyboard in table
1; instead, try table 2 first, then 1: some older keyboards, connected to
a castrated 8042, do not know how to talk in table 1 (or worse, will report
they do while they don't).

If automatic translation is not possible, remember which table the keyboard
ended configured in, and convert the scancodes from table 2 to table 1 if
necessary.

ok kettenis@

First pass at removing clauses 3 and 4 from NetBSD licenses.

Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.

OK deraadt@

Keep running the scancode translation state machine even when the keyboard
is set to raw mode, but only feed decoded events to wscons if non-raw mode.

Then, as an exception to this, pass the audio control keys events to
wscons even if in raw mode, so that the in-kernel mixer control code can
perform its work. The event is also seen by the raw event consumer (i.e.
the X server).

Requested and tested by many...

miod says noone needs isa/isavar.h anymore, and i believe him

use NULL to point to the response buffer, which avoids confusion; ok fgsch

- Remove a shadow declaration.
- Correct resp size.

deraadt@ ok.

default to have pckbd_set_xtscancode() instruct the 8042 to use
table 3, still falling back on table 2 or 1 after carefully checking
that the table set request took

fixes the keyboard on the oqo model 01/01+

in snaps for a while, tested by many

ok miod@

go via pckbc_enqeue_cmd() in pckbd_enable() if on; fixes PR 4615

ok miod@, mickey@

send enable cmd after a reset; form netbsd

typos from Tom Cosgrove;

Remove the advertising clause in the UCB license which Berkeley
rescinded 22 July 1999. Proofed by myself and Theo.

First round of __P removal in sys

Don't include isavar.h on sparc64

branches: 1.2.4; 1.2.8;
Remove dead code.

Machine-independent PC-like keyboard driver; from NetBSD. XXX - Not used
anywhere quite yet, but useful to have these files in the tree while we work
towards wscons for i386 and alpha.

Do not overwrite `table' in the non-translating case.

This ensures the keyboard is using the expected scancode.

From miod@, problem also noticed by Markus Hennecke, ok otto@

pckbd: don't change translation mode if controller is in table 2

This was changed a decade ago to forcibly try table 3 first in order
to make some now-long-gone hardware work.

Newer Lenovo machines seem to have trouble being asked to change
modes which manifests as a long boot delay as it waits for each
request to timeout, or by causing the keyboard to generate junk when
typing.

Assume table 2 by default and just leave it alone if it's already
there. This is how Linux has operated for quite a while and seems
to help on these Lenovo machines.

Tested by a few with these machines and has been in snaps for a bit.

Re-enable pckbd on resume (similar to what we do on boot). Fixes problems
on (at least) various HP laptops that previously had no working keyboard
after resuming from 'zzz'.

Reported by Aleksandar Lakic, who also verified several versions of the
diff during development, thanks.

discussed with miod and kettenis, tested by many others on tech@ - thanks.

Print irq informations in pckbc_set_inputhandler().

ok miod@

Revert 1.39. Resetting after specifically putting the keyboard in a
different table will most likely just revert the keyboard to its
default table anyway.

Instead, just flush the kbd slot before choosing a table and then
still forcefully enable the slot, which is enough to fix UKC on the
3rd gen X1 carbon while having a much smaller chance of breaking
anything else.

ok deraadt

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@

On first cnpoll, reset the keyboard and pms hard. This is required
to make "boot -c" support work on a variety of newer machines.
Do not anticipate this harming older machines, but we'll have to wait
and see with this change in the tree.
with jcs

Speed up the boot sequence by deferring the scan of xt keyboard code set.

If you were wondering why there's a pause of 5 seconds after loading the
kernel and before seeing the copyright in blue when booting some of your
machines, well this is for you!

mlarkin@ found that this delay is caused by some code probing for xt scan
code tables when pckbd(4) initialize the console keyboard. So this diff
implements an idea from deraadt@ to only do the scan once, either during
*attach() or if we enter ddb> or ukc> before that!

ok miod@, mlarkin@, deraadt@, shadchin@

my bad, last commit was not ok deraadt, revert it.

Don't use volume keys when in raw-mode (this doesn't work), and let
Xorg driver do the translation and handle them as regular keys. Fixes
confusion caused by the volume being changed twice in contradictory
ways: once by X programs and once by the pckbd(4) driver.

ok deraadt, kettenis

Attempt to make user changes of keyboard layout a bit more `sticky' on wsmux
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@

backout latest: audio keys can autorepeat. Autorepeated keys are not
decoded by the wskbd layer, thus autorepeted audio keys end-up passed
to userland in raw mode (ie to X), resulting in keyboard input
corruption. Noticed (and debugged) by halex@, thanks.

don't propagate XF86XK_Audio{Lower,Raise}Volume keys to userspace,
otherwise volume may be adjusted twice: once by X apps and once in
the kernel.

feedback from many, ok shadchin@

simplify pckbc_xt_translation()
* call only for set translation on (once in /sys/dev/pckbd.c)
therefore we can delete unused code.
* change behavior (more standard) - return zero on success

ok miod@

Ansify non-ansified function definitions. No functional change.

ok miod@

small cleanup ioctl WSKBDIO_GETLEDS

ok miod@

removed slot argument of function pckbd_cnattach
because it is always PCKBC_KBD_SLOT

ok miod@, krw@

In pckbd_scancode_translate(), correctly translate the break sequence
between scan code sets 1 and 2.

Don't do anything on suspend/resume for now (there is a diff brewing,
but it has some problems still..)

Disable the heuristics for legacy free systems if pckbc flags are set to 1
in UKC; found the hard way by jakemsr@ on an old Tecra laptop.

For DVACT_SUSPEND and DVACT_RESUME we should always return success.

pckbd_activate() should return failure if it knows; ok pirofti

better style is DVACT_SUSPEND before DVACT_RESUME

Fix pckbd and acpihpet suspend/resume cases to fit with the future framework
that's going to get in really soon.

Okay mlarkin@, deraadt@.

Get rid of devact enum, substitute it with an int and coresponding defines.

This is needed for the addition of further suspend/resume actions.

Okay deraadt@, marco@.

Legacy-free PC hardware do not have a real PS/2 keyboard controller, but
rather have the USB HCI emulate it during boot, while legacy mode is enabled.

This causes pckbd0 to attach as the console device, but is lost as soon as
the USB HCI driver attaches.

The disappearance of the emulated PS/2 controller can however be detected
in pckbc(4) - which is supposed to attach after [eou]hci(4), with the controller
refusing to ack commands and replying ``please resend'' instead.

In that case, the kernel will now no longer attach pckbd, and will perform a
new console input device selection, allowing the (real) usb keyboard to
become the console.

Thanks to krw@ for countless tests on legacy-free hardware; also tested on
more conventional hardware by naddy@ and I.

Only amd64 and i386 platforms are affected by this change.

Forgot to add break to the switch cases. Silly.
Okay deraadt@.

Add wake/suspend support for pckbd(4).

Patch initially from mlarkin@. KNF and refactoring by me.
Suggestions and okay deraadt@.

Make sure pckbd_scancode_translate() returns a scancode with the break/release
bit set if needed, in all cases. This fixes rawkbd operation on controllers
which require the kernel to perform scancode translation.

Found by and ok kettenis@

Move #include <dev/pckbc/wskbdmap_mfii.h> after including
dev/wscons/wsksymvar.h where struct wskbd_mapdata gets
declared.

ok miod@

If pckbc_xt_translation() fails, do not try to force the keyboard in table
1; instead, try table 2 first, then 1: some older keyboards, connected to
a castrated 8042, do not know how to talk in table 1 (or worse, will report
they do while they don't).

If automatic translation is not possible, remember which table the keyboard
ended configured in, and convert the scancodes from table 2 to table 1 if
necessary.

ok kettenis@

First pass at removing clauses 3 and 4 from NetBSD licenses.

Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.

OK deraadt@

Keep running the scancode translation state machine even when the keyboard
is set to raw mode, but only feed decoded events to wscons if non-raw mode.

Then, as an exception to this, pass the audio control keys events to
wscons even if in raw mode, so that the in-kernel mixer control code can
perform its work. The event is also seen by the raw event consumer (i.e.
the X server).

Requested and tested by many...

miod says noone needs isa/isavar.h anymore, and i believe him

use NULL to point to the response buffer, which avoids confusion; ok fgsch

- Remove a shadow declaration.
- Correct resp size.

deraadt@ ok.

default to have pckbd_set_xtscancode() instruct the 8042 to use
table 3, still falling back on table 2 or 1 after carefully checking
that the table set request took

fixes the keyboard on the oqo model 01/01+

in snaps for a while, tested by many

ok miod@

go via pckbc_enqeue_cmd() in pckbd_enable() if on; fixes PR 4615

ok miod@, mickey@

send enable cmd after a reset; form netbsd

typos from Tom Cosgrove;

Remove the advertising clause in the UCB license which Berkeley
rescinded 22 July 1999. Proofed by myself and Theo.

First round of __P removal in sys

Don't include isavar.h on sparc64

branches: 1.2.4; 1.2.8;
Remove dead code.

Machine-independent PC-like keyboard driver; from NetBSD. XXX - Not used
anywhere quite yet, but useful to have these files in the tree while we work
towards wscons for i386 and alpha.

pckbd: don't change translation mode if controller is in table 2

This was changed a decade ago to forcibly try table 3 first in order
to make some now-long-gone hardware work.

Newer Lenovo machines seem to have trouble being asked to change
modes which manifests as a long boot delay as it waits for each
request to timeout, or by causing the keyboard to generate junk when
typing.

Assume table 2 by default and just leave it alone if it's already
there. This is how Linux has operated for quite a while and seems
to help on these Lenovo machines.

Tested by a few with these machines and has been in snaps for a bit.

Re-enable pckbd on resume (similar to what we do on boot). Fixes problems
on (at least) various HP laptops that previously had no working keyboard
after resuming from 'zzz'.

Reported by Aleksandar Lakic, who also verified several versions of the
diff during development, thanks.

discussed with miod and kettenis, tested by many others on tech@ - thanks.

Print irq informations in pckbc_set_inputhandler().

ok miod@

Revert 1.39. Resetting after specifically putting the keyboard in a
different table will most likely just revert the keyboard to its
default table anyway.

Instead, just flush the kbd slot before choosing a table and then
still forcefully enable the slot, which is enough to fix UKC on the
3rd gen X1 carbon while having a much smaller chance of breaking
anything else.

ok deraadt

Remove some includes include-what-you-use claims don't
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@

On first cnpoll, reset the keyboard and pms hard. This is required
to make "boot -c" support work on a variety of newer machines.
Do not anticipate this harming older machines, but we'll have to wait
and see with this change in the tree.
with jcs

Speed up the boot sequence by deferring the scan of xt keyboard code set.

If you were wondering why there's a pause of 5 seconds after loading the
kernel and before seeing the copyright in blue when booting some of your
machines, well this is for you!

mlarkin@ found that this delay is caused by some code probing for xt scan
code tables when pckbd(4) initialize the console keyboard. So this diff
implements an idea from deraadt@ to only do the scan once, either during
*attach() or if we enter ddb> or ukc> before that!

ok miod@, mlarkin@, deraadt@, shadchin@

my bad, last commit was not ok deraadt, revert it.

Don't use volume keys when in raw-mode (this doesn't work), and let
Xorg driver do the translation and handle them as regular keys. Fixes
confusion caused by the volume being changed twice in contradictory
ways: once by X programs and once by the pckbd(4) driver.

ok deraadt, kettenis

Attempt to make user changes of keyboard layout a bit more `sticky' on wsmux
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@

backout latest: audio keys can autorepeat. Autorepeated keys are not
decoded by the wskbd layer, thus autorepeted audio keys end-up passed
to userland in raw mode (ie to X), resulting in keyboard input
corruption. Noticed (and debugged) by halex@, thanks.

don't propagate XF86XK_Audio{Lower,Raise}Volume keys to userspace,
otherwise volume may be adjusted twice: once by X apps and once in
the kernel.

feedback from many, ok shadchin@

simplify pckbc_xt_translation()
* call only for set translation on (once in /sys/dev/pckbd.c)
therefore we can delete unused code.
* change behavior (more standard) - return zero on success

ok miod@

Ansify non-ansified function definitions. No functional change.

ok miod@

small cleanup ioctl WSKBDIO_GETLEDS

ok miod@

removed slot argument of function pckbd_cnattach
because it is always PCKBC_KBD_SLOT

ok miod@, krw@

In pckbd_scancode_translate(), correctly translate the break sequence
between scan code sets 1 and 2.

Don't do anything on suspend/resume for now (there is a diff brewing,
but it has some problems still..)

Disable the heuristics for legacy free systems if pckbc flags are set to 1
in UKC; found the hard way by jakemsr@ on an old Tecra laptop.

For DVACT_SUSPEND and DVACT_RESUME we should always return success.

pckbd_activate() should return failure if it knows; ok pirofti

better style is DVACT_SUSPEND before DVACT_RESUME

Fix pckbd and acpihpet suspend/resume cases to fit with the future framework
that's going to get in really soon.

Okay mlarkin@, deraadt@.

Get rid of devact enum, substitute it with an int and coresponding defines.

This is needed for the addition of further suspend/resume actions.

Okay deraadt@, marco@.

Legacy-free PC hardware do not have a real PS/2 keyboard controller, but
rather have the USB HCI emulate it during boot, while legacy mode is enabled.

This causes pckbd0 to attach as the console device, but is lost as soon as
the USB HCI driver attaches.

The disappearance of the emulated PS/2 controller can however be detected
in pckbc(4) - which is supposed to attach after [eou]hci(4), with the controller
refusing to ack commands and replying ``please resend'' instead.

In that case, the kernel will now no longer attach pckbd, and will perform a
new console input device selection, allowing the (real) usb keyboard to
become the console.

Thanks to krw@ for countless tests on legacy-free hardware; also tested on
more conventional hardware by naddy@ and I.

Only amd64 and i386 platforms are affected by this change.

Forgot to add break to the switch cases. Silly.
Okay deraadt@.

Add wake/suspend support for pckbd(4).

Patch initially from mlarkin@. KNF and refactoring by me.
Suggestions and okay deraadt@.

Make sure pckbd_scancode_translate() returns a scancode with the break/release
bit set if needed, in all cases. This fixes rawkbd operation on controllers
which require the kernel to perform scancode translation.

Found by and ok kettenis@

Move #include <dev/pckbc/wskbdmap_mfii.h> after including
dev/wscons/wsksymvar.h where struct wskbd_mapdata gets
declared.

ok miod@

If pckbc_xt_translation() fails, do not try to force the keyboard in table
1; instead, try table 2 first, then 1: some older keyboards, connected to
a castrated 8042, do not know how to talk in table 1 (or worse, will report
they do while they don't).

If automatic translation is not possible, remember which table the keyboard
ended configured in, and convert the scancodes from table 2 to table 1 if
necessary.

ok kettenis@

First pass at removing clauses 3 and 4 from NetBSD licenses.

Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.

OK deraadt@

Keep running the scancode translation state machine even when the keyboard
is set to raw mode, but only feed decoded events to wscons if non-raw mode.

Then, as an exception to this, pass the audio control keys events to
wscons even if in raw mode, so that the in-kernel mixer control code can
perform its work. The event is also seen by the raw event consumer (i.e.
the X server).

Requested and tested by many...

miod says noone needs isa/isavar.h anymore, and i believe him

use NULL to point to the response buffer, which avoids confusion; ok fgsch

- Remove a shadow declaration.
- Correct resp size.

deraadt@ ok.

default to have pckbd_set_xtscancode() instruct the 8042 to use
table 3, still falling back on table 2 or 1 after carefully checking
that the table set request took

fixes the keyboard on the oqo model 01/01+

in snaps for a while, tested by many

ok miod@

go via pckbc_enqeue_cmd() in pckbd_enable() if on; fixes PR 4615

ok miod@, mickey@

send enable cmd after a reset; form netbsd

typos from Tom Cosgrove;

Remove the advertising clause in the UCB license which Berkeley
rescinded 22 July 1999. Proofed by myself and Theo.

First round of __P removal in sys

Don't include isavar.h on sparc64

branches: 1.2.4; 1.2.8;
Remove dead code.

Machine-independent PC-like keyboard driver; from NetBSD. XXX - Not used
anywhere quite yet, but useful to have these files in the tree while we work
towards wscons for i386 and alpha.