ioasic), and use those attributes to pull in appropriate files.
le_ioasic now has needs-flag, but le doesn't; the flag is only necessary
on systems configured with IOASIC-attached LANCE chips.
remove their 'integrate' (usually defined to be 'static') keywords.
when lance drivers are split up by attachment, more than one file will
reference the copy/zero functions (i.e. not just the file that pulls in
am7990.c... and eventually inclusion of am7990.c should go away entirely).
chip-independent clock code. 'clock' has been renamed 'mcclock' 'clock'
has been renamed 'mcclock' (since it's a driver for that particular
clock, and since eventually there may be another clock chip driver),
and now attaches via seperate match/attach functions to both TC and ISA.
This removes a whole lot of #ifdefs...
'cflag' for the console. Normally set to TTYDEF_CFLAG, may be
overridden by machine-dependent console attachment code, as necessary.
(Alpha uses it to set cs8 -parenb.) Files including comvar.h now
need to include <sys/termios.h>, because comconscflag is of type
tcflag_t.
if people define EXPORTABLE_SYSTEM, they REALLY don't want to do stuff
in 'domestic'. Pay attention to it when doing 'make build'.
in 'make build', install share/mk _first_, because include dirs may
require new make templates.
in 'make build', install domestic includes after normal includes, so
they can previously-installed includes if necessary.
Note that all of domestic/lib should be built in 'make build' during the
library build stage.
looking for "${MAKECONF}", or failing that, "/etc/mk.conf" and including
the first one it finds, if it exists. From Chris Demetriou <cgd@netbsd.org>,
PR #1970.
source file to libkern, it should be added to _ALL_ ports makefiles if
it is machine-independent and used by machine-independent code (in
this case adosfs). (There are several arguments that say that
strncasecmp should not be in libkern at all, and i think they're
good ones, but as long as ADOSFS needs it to link, it has to be here
for all architectures.)
from the current apecs_pci.c. This new version hopefully works for
the same sets of devices that that previous one did, and hopefully
will work for multi-function devices and for secondary PCI busses as
well. (looking at the code, there was no way the old one could have!)
documented behavior. sysctl(3) is documented to return 0 on success,
-1 on failure. The previous behavior was to return -1 on failure
and the number of bytes copied back down to user space.
Fixes part of PR #1999, from Kevin M. Lahey <kml@nas.nasa.gov>
cgd