src-test/usr.sbin/kbdcontrol, branch stable/7 FreeBSD source tree https://cgit-dev.freebsd.org/src-test/atom?h=stable%2F7 2006-11-16T13:43:05Z Grammar fix from Ceri. 2006-11-16T13:43:05Z Ruslan Ermilov ru@FreeBSD.org 2006-11-16T13:43:05Z urn:sha1:c5233647e2f873efbfa3d4fefc82bcfc770778cb Document that visual bell is the global setting, while 2006-11-16T12:37:35Z Ruslan Ermilov ru@FreeBSD.org 2006-11-16T12:37:35Z urn:sha1:b59cc9bbf4a37ae17de7bafab020593cd854b811 other bell types can be set individually for each vty. Replace magic numbers for console bell types with defines. 2006-11-16T12:27:51Z Ruslan Ermilov ru@FreeBSD.org 2006-11-16T12:27:51Z urn:sha1:5a66b66324ec6d44e260932d754b2437e9de9499 Markup fixes. 2006-09-29T17:57:04Z Ruslan Ermilov ru@FreeBSD.org 2006-09-29T17:57:04Z urn:sha1:bc84aa4ba392b392f15d988ddf09682340668672 Make op parameter to mux_keyboard() u_int instead of int. 2006-09-15T18:41:12Z Maksim Yevmenkin emax@FreeBSD.org 2006-09-15T18:41:12Z urn:sha1:eb65c05e4491e5376db2cade8b8b056a581046d3 This should fix sparc64 messages like Sep 15 11:17:39 peahi kernel: WARNING pid 5477 (kbdcontrol): ioctl sign-extension ioctl ffffffff80244b45 PR: sparc64/96798 MFC after: 1 week Reveal sacred spells necessary for putting kbdmux(4) to real use. 2005-12-29T20:11:46Z Maxim Sobolev sobomax@FreeBSD.org 2005-12-29T20:11:46Z urn:sha1:ec5bf798690767250d8c3f556d920123bdfa8a83 Hopefully gods of RTFS and RTFCL will not go after me. - Fix spelling of 'multiplexer' 2005-07-21T22:50:31Z Markus Brueffer markus@FreeBSD.org 2005-07-21T22:50:31Z urn:sha1:9519511c6a133ad460fc5b4f3d2976983da28ab6 - Grammar fixes Approved by: simon MFC after: 3 days kbdmux(4) keyboard multiplexer integration 2005-07-14T22:43:20Z Maksim Yevmenkin emax@FreeBSD.org 2005-07-14T22:43:20Z urn:sha1:4673ea01e3d85d63317d3c7322b2fed979efa114 o Slightly change KBADDKBD and KBRELKBD ioctl() interface. Instead of passing keyboard index pass keyboard_info_t structure with populated 'kb_unit' and 'kb_name' fields. Keyboard index is not very user-friendly and is not very easy to obtain. Keyboard driver name and unit, on the other hand, is much more user friendly and known almost all the time; o Move definition of keyboard_info_t structure up; o Teach kbdcontrol(1) how to attach/detach keyboards to/from the keyboard multiplexor; o Update kbdcontrol(1) man page and document new functionality. To attach/detach keyboard to/from keyboard multiplexor one needs to use keyboard device name (i.e. ukbd0). MFC after: 1 week Sort sections. 2005-01-18T20:02:45Z Ruslan Ermilov ru@FreeBSD.org 2005-01-18T20:02:45Z urn:sha1:59a3c79da68b53e9d606f0b7991574d982a843e1 Change the USB keyboard example to use /dev/ukbd0 instead of /dev/kbd1. 2005-01-08T06:02:56Z Brooks Davis brooks@FreeBSD.org 2005-01-08T06:02:56Z urn:sha1:539905192f906dc838ad88af4ac11e7814bc0a12 This example caused me to incorrectly believe that you must use the generic device nodes when you can in fact use either. It's often better to use the driver specific node.