FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F14.3 2023-10-16T07:16:01Z 2023-10-16T07:16:01Z Konstantin Belousov kib@FreeBSD.org 2023-10-02T22:25:52Z urn:sha1:23a55498a8184add2396479a09c7ba0921d057a4 (cherry picked from commit 6e92fc930943a85f311e986a02e2b3dae9e37126) 2023-08-16T17:54:18Z Warner Losh imp@FreeBSD.org 2023-08-16T17:54:18Z urn:sha1:2ff63af9b88c7413b7d71715b5532625752a248e Remove /^\s*\*+\s*\$FreeBSD\$.*$\n/ 2023-07-07T05:10:18Z Michael git@paepcke.de 2023-07-07T02:32:45Z urn:sha1:971bac5ace7a3c2262349fa2808188a11a5ffeed Refactor to eliminate duplicated rate and delay tables, with minor style tweaks for changed lines. Remove an obsolete comment about needing to convert from microseconds to ticks (that's done elsewhere). Remove traiing whitespace in kbdcontrol.c. Except for the new warning, no change in behavior Sponsored by: DSS GmbH Reviewed by: imp [minor style tweaks as well] Pull Request: https://github.com/freebsd/pull/683 Differential Revision: https://reviews.freebsd.org/D38818 2023-05-12T16:44:03Z Warner Losh imp@FreeBSD.org 2023-05-10T15:40:58Z urn:sha1:4d846d260e2b9a3d4d0a701462568268cbfe7a5b The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause. Discussed with: pfg MFC After: 3 days Sponsored by: Netflix 2023-02-14T13:03:28Z Stefan Eßer se@FreeBSD.org 2023-02-14T13:03:28Z urn:sha1:f20058955c9d1041a5a09cd02a27babda7e34dc8 FreeBSD-9 had introduced support for the full set of Unicode characters to the parsing and processing of keymap character tables. This support has been extended to cover the table for accented characters that are reached via dead key combinations in FreeBSD-13.2. New ioctls have been introduced to support both the pre-Unicode and the Unicode formats and keyboard drivers have been extended to support those ioctls. This commit makes the ABI compatibility functions in the kernel optional and dependent on COMPAT_FREEBSD13 in -CURRENT. The kbdcontrol command in -CURRENT and 13-STABLE (before 13.2) has been made ABI compatible with old kernels to allow a new world to be run on an old kernel (that does not have full Unicode support for keymaps). This commit is not to merged back to 12-STABLE or 13-STABLE. It is part of review D38465, which has been split into 3 separate commits due to different MFC and life-time requirements of either commit. Approved by: imp Differential Revision: https://reviews.freebsd.org/D38465 2023-02-06T22:48:47Z Stefan Eßer se@FreeBSD.org 2023-02-06T22:48:47Z urn:sha1:4972fb9276389fb87a790b415b1161cff395884c Support for Unicode characters had been added to the keyboard code, but there are keymaps that have accented characters accessed via dead key combinations, and those were still restricted to 8 bit codes. This update to kbd.c adds support for Unicode characters and compatibility code that allows a kbdcontrol command built from kbio.h without these patches to work on a new kernel. Compatibility code that allows a new kbdcontrol binary running on an old kernel to load and display the dead key map will be committed in a separate commit. Reviewed by: imp, brooks Approved by: brooks MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D38381 2020-09-01T21:48:55Z Mateusz Guzik mjg@FreeBSD.org 2020-09-01T21:48:55Z urn:sha1:875af9c6afa41465949b0664f8363ac8fc731543 2019-12-26T17:09:36Z Kyle Evans kevans@FreeBSD.org 2019-12-26T17:09:36Z urn:sha1:2899979df9b03e4c1fa45be3075dc8c47a11fdb5 r356087 made it rather innocuous to double-register built-in keyboard drivers; we now set a flag to indicate that it's been registered and only act once on a registration anyways. There is no misleading here, as the follow-up kbd_delete_driver will actually remove the driver as needed now that the linker set isn't also consulted after kbdinit. 2019-12-16T16:41:24Z Kyle Evans kevans@FreeBSD.org 2019-12-16T16:41:24Z urn:sha1:5a7a578be9e92e1ceb16fced892a9e4f2eba1712 Keyboard drivers are generally registered via linker set. In these cases, they're also available as kmods which use KPI for registering/unregistering keyboard drivers outside of the linker set. For built-in modules, we still fire off MOD_LOAD and maybe even MOD_UNLOAD if an error occurs, leading to registration via linker set and at MOD_LOAD time. This is a minor optimization at best, but it keeps the internal kbd driver tidy as a future change will merge the linker set driver list into its internal keyboard_drivers list via SYSINIT and simplify driver lookup by removing the need to consult the linker set. 2019-12-16T02:44:56Z Kyle Evans kevans@FreeBSD.org 2019-12-16T02:44:56Z urn:sha1:eefc662f0b08ea2a9e704d911671984547d6a3ab Most keyboard drivers are using the genkbd implementations as it is; formally use them for any that aren't set and make genkbd_get_fkeystr/genkbd_diag private.