sys/dev/uart/uart_kbd_sun.c 1.10, 1.11 (partial), 1.13;
sys/dev/uart/uart_kbd_sun.h 1.3; sys/sparc64/conf/NOTES 1.30
- In sunkbd_probe_keyboard() don't bother to determine the keyboard layout
as we have no use for that info. Instead let this function return the
keyboard ID and verify at its invocation in sunkbd_configure() that we're
talking to a Sun type 4/5/6 keyboard, i.e. a keyboard supported by this
driver.
- Add an option SUNKBD_EMULATE_ATKBD whose code is based on the respective
code in ukbd(4) and like UKBD_EMULATE_ATSCANCODE causes this driver to
emit AT keyboard/KB_101 compatible scan codes in K_RAW mode as assumed by
kbdmux(4). Unlike UKBD_EMULATE_ATSCANCODE, SUNKBD_EMULATE_ATKBD also
triggers the use of AT keyboard maps and thus allows to use the map files
in share/syscons/keymaps with this driver at the cost of an additional
translation (in ukbd(4) this just is the way of operation).
- Implement an option SUNKBD_DFLT_KEYMAP, which like the equivalent options
of the other keyboard drivers allows to specify the default in-kernel
keyboard map. For obvious reasons this made to only work when also using
SUNKBD_EMULATE_ATKBD.
- Implement sunkbd_check(), sunkbd_check_char() and sunkbd_clear_state(),
which are also required for interoperability with kbdmux(4).
- Implement K_CODE mode and FreeBSD keypad compose.
- As a minor hack define KBD_DFLT_KEYMAP also in the !SUNKBD_EMULATE_ATKBD
case so we can obtain fkey_tab from <dev/kbd/kbdtables.h> rather than
having to duplicate it and #ifdef some more code.
- Don't use the TX-buffer for writing the two command bytes for setting the
keyboard LEDs as this consequently requires a hardware FIFO that is at
least two bytes in depth, which the NMOS-variant of the Zilog SCCs doesn't
have. Thus use an inlined version of uart_putc() to consecutively write
the command bytes (a cleaner approach would be to do this via the soft
interrupt handler but that variant wouldn't work while in ddb(4)). [1]
- Fix some minor style(9) bugs.
PR: 90316 [1]
to become unkillable when that process is sent a termination signal. The
process will sit in waitvt looping in the kernel, and chewing up all
available CPU until the system is rebooted.
Note: this is not an MFC as this code no longer exists in HEAD. However,
this is based on the same syscons fix which was just MFC'd after one week
in HEAD.
Reviewed by: bde
Fix a bug that will cause a process that calls the VT_WAITACTIVE ioctl
to become unkillable when that process is sent a termination signal. The
process will sit in waitvt looping in the kernel, and chewing up all
available CPU until the system is rebooted.
Submitted by: Jilles Tjoelker <jilles@stack.nl>
Reviewed by: bde
date: 2007/08/30 21:18:42; author: njl; state: Exp; lines: +32 -7
Evaluate _OSC on boot to indicate our OS capabilities to ACPI. This is
needed at least to convince the BIOS to give us access to CPU freq
control on MacBooks.
Approved by: njl (mentor)
ensure the head entry of addrinfo chain has non-NULL ai_canonname to be
compliant with RFC3493.
PR: standards/114910
Approved by: ume (mentor)
lib/libc/net/getaddrinfo.c: 1.86
Dutch calendar
More dates: Sint Maarten, Dierendag, Trinitatis
Fix spelling: Carnaval
Add more of the Royal Family.
Croation calendars:
Update to calendar/calendars/hr_HR.ISO_8859-2/calendar.praznici
with fixes and new dates.
PR: conf/26658
Submitted by: Josip Rodin <joy@gkvk.hr>
Original PR description:
man(1) can't handle compressed included files.
Some ports will install with compressed manpages. man handles
this by looking for the .gz version of a man source file.
It is also common to include other files with the .so
directive where commands or functions share a man page.
Traditionally ports have had to handle this by either not
compressing the manpages, or using the _MLINKS macro in the
port makefile to create symlinks to the actual source file,
rather than using .so versions. Notably, the current version
of Xorg port breaks. See ports/113096 and ports/115845.
PR: bin/115850
Submitted by: Callum Gibson <callumgibson@optusnet.com.au>
and always require the queue to be specified to reduce diffs with HEAD.
These APIs are internal APIs only used to implement higher level primitives
such as locks and condition variables.
Approved by: alfred
where a reader blocked on a lock with no owner and just assert that it
never happens like HEAD.
- Actually set td->td_tsqueue to the sub-queue of a turnstile that a
thread is actually enqueued to. Otherwise, the kernel would always
think that threads were on the queue for exclusive (write) waiters
(queue 0). Thus, if the priority of a thread waiting on a read lock
was adjusted while it was waiting it could result in corrupting the
queue of waiting threads.
Revision Path
1.82 src/etc/rc.d/Makefile
1.16 src/etc/rc.d/lockd
1.17 src/etc/rc.d/lockd
1.18 src/etc/rc.d/lockd
1.15 src/etc/rc.d/nfslocking
1.16 src/etc/rc.d/statd
1.17 src/etc/rc.d/statd
Split rc.d/nfslocking into two separate scripts: rc.d/lockd
and rc.d/statd. Keep rc.d/nfslocking for POLA reasons but do
not run it during system startup.
PR: conf/107316
Revision Path
1.14 src/etc/rc.d/nfslocking
The precmd routine does not need to check whether the comman
should be "forced". If some pre-condition is not met, it should
fail as it normally does and rc.subr(8) will make the appropriate
decision. Incidentally, the previous behaviour had a bug where
the "force" flag was respected only when checking rc.conf(5) knobs.
The flag was ignored when verifying the rpcbind(8) dependency.
Fix a DIV0 in case a large value for fs_avgfilesize or fs_avgfpdir
is given (with newfs or tunefs) and dirsize overflows.
In case dirsize is <= 0 because of an overflow set maxcontigdirs
to 0 so it will be 1 later. This is what would happen for large
fs_avgfilesize. [1]
Submitted by: pjd [1]
Fix an incorrect PCI device id. The current value conflicts with
the mfi(4) LSI MegaSAS RAID card. Looking at the Linux driver for the
mpt(4) it should be 0x0062 and not 0x0060. Tested with an mfi card
of this device id.
Reviewed by: scottl
