v_caddr_t with extreme prejudice. Here the bogons were originally
the same as for c_caddr_t (half-baked K&R support), but rev.1.95
changed one wrong cast and one harmless cast to 2 wrong casts,
and rev.1.96 only fixed the originally wrong cast.
is not implied by -Wall as claimed by gcc.1. Adding it causes a
measly 7193 new warnings for LINT, mostly for "unused parameter" and
"comparison between signed and unsigned".
terminating c_caddr_t with extreme prejudice. Here we depended
on the "opaque" type c_caddr_t being precisely `const char *'
to do unportable pointer arithmetic.
c_caddr_t with extreme prejudice. Here the original casts to
caddr_t were to support K&R compilers (or missing prototypes),
but the relevant source files require an ANSI compiler.
problem and solution is outlined in the comments, but basically
we needed a way to allow the SYSINIT mechanism to handle const void *
arguments and function pointers as well as non-const arguments and
function pointers while still maintaining the compiler's ability to
issue warnings if you try to use a bad combination.
c_caddr_t with extreme prejudice. Here the point of the original
cast to caddr_t was to break the warning about the const mismatch
between write(2)'s `const void *buf' and `struct uio's `char
*iov_base' (previous bitrot gave a gratuitous dependency on caddr_t
being char *). Compiling with -Wcast-qual made the cast a full
no-op.
This change has no effect on the warning for discarding `const'
on assignment to iov_base. The warning should not be fixed by
splitting `struct iovec' into a non-const version for read()
and a const version for write(), since correct const poisoning
would affect all pointers to i/o addresses. Const'ness should
probably be forgotten by not declaring it in syscalls.master.
c_caddr_t with extreme prejudice. Here we want to convert from
`const char *' to `const char *'. Casting through c_caddr_t is
not the way to do this. The original cast to caddr_t was apparently
to break warnings about const mismatches in other versions of BSD
(in 4.4BSDLite2, the conversion is from `const char *path' to
plain caddr_t).
Add C_DECLARE_MODULE - same as DECLARE_MODULE but uses C_SYSINIT
instead of SYSINIT.
The C_ items are going to be used for items passing const data to
sysinit.
the interrupt which will be given to the PCIC. If the value supplied is
illegal or not available, interrupts will be turned off and polled mode
used instead.
apparently in accordance with style(9).
Complained-about-by: bde
vinumopen: Change check for root user to a call to suser(9)
vinumclose: Remove check for root user.
Nitpicked-by: phk
let it rotate /var/log/wtmp again, and update monthly/200.accounting to
take this into account. (Some sites might want to change the parameters
of the rotation; it's easier to do this when it's all centralized in
newsyslog.conf.)
Auto Detection Mode. This leaves MSP3400C owners still unsupported.
Thanks to Gerd Knorr <kraxel@cs.tu-berlin.de> for providing some early
assistance and sample code in the linux bttv driver.
Nicolas Souchu <nsouch@freebsd.org> ported the msp_read/write/reset
functions to smbus/iicbus.
METEOR_INPUT_DEV2 now selects a composite camera on the SVIDEO port.
For true SVIDEO, use METEOR_INPUT_DEV_SVIDEO.
If you get a monochrome image from the SVIDEO port, you have
seleted the wrong input type.
Tested by: Johan Larsson<gozer@ludd.luth.se>
version and a const void * version. Currently the const void * version
simply calls the void * version ( i.e. no 'fix' is in place ).
A solution needs to be found for the C_SYSINIT ( etc...) family of
macros that allows const void * without generating a warning, but
does not allow non-const void *.
Sun implemented iBCS2 compatibility on Solaris >= 2.6: The emulator
runs in user-mode, patching the LDT so that client programs making
syscalls through the old iBCS2 call gate get handled by the emulator
process. Unemulated syscalls therefore need their own call-gate that
bypasses the emulator. Sun chose LDT entry 4 to implement this, which
is what we've been using as LUDATA_SEL, so we need to change LUDATA_SEL
if we want to run Solaris executables.
Discussed with: Mike Smith
keyboard.
- Translate some keycode for the 84 keyboard so that the 84 keyboard
and the 101 keyboard become more compatible in terms of keycodes.
- Updated the built-in keymaps so that it is in line with the recent
changes in share/syscons/keymaps.
- Added some comment on the Pause/Break key on the 101 keyboard.
- The numpad * key should always generate *.
- The numpad - is fkey52 and should not generate a control code (0x1f).
- The numpad 5 is fkey54, not fkey61.
- The numpad 6 is fkey55 and should not generate a control code (0x1e).
- Fix Spanish keymap.
PR: i386/9532
Submitted by jose@we.lc.ehu.es.
- Added Croatian keymap. It is the same as the Slovenian keymap.
PR: misc/9706
Pointed out by: Damjan Marion
- Addef Finnish keymap. It is the same as the Swedish keymap.
PR: bin/9632
Submitted by: Martti Kuparinen
- Assign special functions consistently in all keymap files.
101 keyboard 84 keyboard function
------------------------------------------------------------------------
Ctrl-Alt-Delete Ctrl-Alt-Delete reboot
Ctrl-Alt-Esc Ctrl-Alt-Esc debug
Ctrl-Alt-Space Ctrl-Alt-Space susp
ScrollLock ScrollLock slock
PrintScreen Shift-(Numpad *)/PrintScreen nscr
Ctrl-PrintScreen Shift-Ctrl-(Numpad *)/PrintScreen debug
Alt-PrintScreen/SysRq SysRq nop
Pause Ctrl-NumLock slock
Shift-Pause Shift-Ctrl-NumLock saver
Alt-Pause Alt-Ctrl-NumLock susp
Ctrl-Pause/Break Ctrl-ScrollLock/Break nop
Left W*ndow key NA fkey62
Right W*ndow key NA fkey63
Menu NA fkey64
NOTE: us.unix.kbd and us.emacs.kbd are very much different from the
other keymaps, thus, I didn't touch them.
vinum_scandisk: check not only drive error, but also drive state,
before accessing the drive.
drivecmp: Remove warning messages by Backing out overly constant
declarations in revision 1.9.
