Add MODULE glue and build infrasructure.

XXX We won't actually build or install it due to kern/59716 but
XXX it can be manually built and installed if you want.

Disable a few modules that need serious work to build.

Add if_rge to the list of {bus,attachment}-specific modules

A driver and userland utility for a couple of families of the
Microchip Technology / SMSC fan controller chips.

The driver and utility supports the:

o EMC2101 and EMC2101-R
o EMC2103-1, EMC2102-2 and EMC2103-4
o EMC2104
o EMC2106
o EMC2301
o EMC2302
o EMC2303
o EMC2305

The EMC210X family supports 1 or 2 fans with tachometer. Depending on
the chip, it may support 2 additional fans without tach and might
support a high side attachment (i.e. a fan, usually 5v, driven
directly from the chip and not PWM or DAC). All versions of EMC210X
support internal temperature measurements, and depending on the chip,
may support up to 5 additional temperature zones. The tachometers and
temperature measurements are provided to the system via the envsys(4)
framework. Some chip types support GPIO pins and support is provided
via the gpio(4) framework.

The EMC230X family supports 1, 2, 3 or 5 fans with the same number of
tachometers. No temperature zone or GPIO support. The tachometers
are provided to the system via the envsys(4) framework. The fan
support can be provided by PWM signaling or DAC.

The two chip families mostly do PWM signaling for the fan speed, but a
number of them support DAC output, a 0 to 3v or so voltage. When the
chip supports external temperature zones, this is done usually by a
bipolar NPN or PNP transister configured as a diode, but some of the
chip varients support thermistors.

The emcfan(4) kernel driver provides a simple read / write / seek
device in /dev/ to the register set in the chip. The heavy lifting is
done in the userland utility emcfanctl(8) which provides the ability
to read and write to any valid register and provides some basic higher
level commands to control fan behavior. The output is simple text
lines, or JSON.

The kernel driver does not reset or other mess with the chip, aside
from reading registers. It is entirely possible that something else
in any particular system is the major manager of the fan controller
and it would not do for the kernel driver to mess too much with the
attached device. All interactions are intentional via the userland
utility.

It is known that a EMC2301 is present on the Raspberry PI 4 Compute IO
module (not to be confused with the Raspberry PI 4 Compute module
itself) and there is a breakout board from Adafruit with a EMC2101 on
it. The chips themselves are pretty inexpensive from Mouser or
Digi-key and can be soldered using the simpler SMD soldering
techniques. A number of the variants are QFN packages, but the pads
are exposed to the side of the chip. No other external components are
required to use these fan controllers.

A driver for the DS28E17 1-Wire to I2C bridge chip.

This chip acts like a 1-Wire slave device and provides a iic(4) master
at the end of the 1-Wire bus. More or less it is the polar opposite
of the DS2482 [ds2482ow(4)] chip.

This device couples well with ds2482ow(4) and can be used to provide a
I2C bus at very great lengths from the controlling computer.

All features of the chip are supported, except for 1-Wire overdrive
support, which requires more work from the onewire(4) infrastructure.

The chip does not support Read without Stop. Attempts to do this will
get turned into a Read with Stop and one will have to hope for the
best. The chip also does not support zero length I2C reads or zero
length I2C writes. This has the side effect of making the default
mode, a zero length I2C write, for i2scan(8) return false positives.
The alternative mode that i2cscan(8) can use, the single byte read,
should work as expected.

The chip has automatic support for end devices that do I2C clock
stretching.

It was noticed that this chip does not work with the gpioow(4) driver.
That might be an interesting thing to debug if one has a good logic
analyzer on hand. While the presence pulse is detected, the gpioow(4)
driver is not able to complete the initial ROM enumeration. The
DS28E17 works flawlessly when driven by a DS2482 [ds2482ow(4)] driver
chip. Poke me if you want any more details.

The chip is pretty inexpensive and only requires a single cap to get
it hooked up. However, the package it comes in is only a 16-QFN
package, so it could provide to be hard to solider onto a board for
some. There are side tabs, so it was possible with a very small iron
and lots of flux. There is a slightly expensive breakout board sold
by Mikroe that probably works well -> https://www.mikroe.com/1-wire-i2c-click

Add ncm(4) a driver for USB Network Control Model

Seen on my Google Pixel 8, which implements ncm instead of urndis.

Add a driver for the Maxim DS2482-100 and DS2482-800 I2C to 1-Wire
bridge.

This chip provides a I2C device that then has 1 or 8 1-Wire busses on
the other side. The 1-Wire buses show up as onewire(4) buses in the
NetBSD.

The chip can be used in situations where:

* You have a I2C bus extended a long distance, say with a LTC4311
active terminator / extender or one of the differential I2C
extenders and you would like to have a 1-Wire device on the far end
and it isn't possible to add wiring to get to the far end.

* You are either out of GPIO pins or the GPIO pins are not reliable
enough to use gpioow(4), but you do have working I2C.

The DS2482 does all of the 1-Wire signals in hardware and provides for
a couple of pullup options for the 1-Wire devices.

All of the functions of the DS2482-100 and -800 are supported except
for overdrive speed support. To do this will likely require some API
changes to onewire(4).

Breakout boards exist for the DS2482 for both variants, but they
appear to be more expensive than expected. The chip itself is quiet
cheap and wasn't all that hard to SMD solder to a board. No other
components are really needed.

There are other members in the same family, the DS2482-101, DS2484 and
DS2485. The DS2482-101 has a sleep pin, but from the datasheet
appears to program the same as the -100 variant. The DS2484 has a
slightly different way to set configuration information and probably
won't quite work with the driver, but isn't far off. The DS2485 is
very different and would require a new driver to function.

acpivmgenid(4): New driver for virtual machine generation ID.

Added to amd64/ALL and i386/ALL kernel configurations, and made
available as a loadable module acpivmgenid.kmod on x86, for now.

TBD: Add to all ACPI-supporting GENERIC kernels.

PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM
fork

modules: Build `ipl` module only if MKIPFILTER is enabled

branches: 1.290.2;
Oooppss remove some local change that was accidentally committed

Don't build the compat_110 module yet - there's no release_110 with which
we can be compatable.

sys/modules: Don't make compat_110.

Eventually we'll need this but it doesn't make sense until 11.0 is
released.

version dup3

port-arm/58194: Resurrect vmt(4) from bitrot

On this architecture vmt(4) used to search for a node "/hypervisor" in the
FDT and probed the VMware hypervisor call only when the node was
found. However, things appear to have changed and VMware no longer provides
the FDT node.

Since vmt(4) doesn't actually need to read anything from FDT, and the
hypervisor call logically resides in virtual CPUs themselves, it would be
better to attach it directly to cpu, just like how it's probed on x86.

bsd.own.mk: Enable MKLSJIT on aarch64.

Make sure there's only one copy of the conditional, in bsd.own.mk;
just make sys/modules/Makefile conditional on MKSLJIT so we don't
have to keep these in sync.

As a workaround for PR 58106, tweak the conditional definition of
SLJIT_CACHE_FLUSH to use cpu_icache_sync_range only in _HARDKERNEL,
and use __builtin___clear_cache in userland and in rump kernels.

PR 58103: bpfjit.kmod is not built on aarch64

acpihed(4): New driver for PNP0C33 to notify apei(4).

PNP0C33 denotes the ACPI Hardware Error Device, which exists only to
be a vector for event notifications.

PR kern/58046

apei(4): New driver for ACPI Platform Error Interfaces.

For now it is wired up only in x86 ALL kernels, and built as a module
for x86 and Arm. Once it gets a little more testing on machines with
APEI, I would like to flip it on by default.

PR kern/58046

skip this subdir for "make includes".

it's excessively slow and does nothing (nor should it.)

Unhook radeondrm module from the build; it doesn't work, and
it's just tempting someone to try it. Leave the files around
in case someone wants to pursue making this work.

Should address kern/57793

XXX Related modules from the same legacy era should probably be
XXX removed, too, but so far only radeondrm has been reported
XXX as an issue. Kep an eye out for sisdrm, savagedrm, tdfxdrm,
XXX and r128drm.

make owtemp a module

viadrmums(4): build legacy VIA DRM UMS driver module for amd64.

This driver is not built-in by default, thus loadable module can help (un)lucky
owners of 64-bit capable VIA (Nano/Eden) systems or early AMD/Intel systems
with some VIA chipsets, which include VIA integrated graphics.
I also boldly added product IDs for few later models from VX8xx/VX9xx chipsets
without 3D support (DX9_0) to "expand" the driver support to more systems.
Tested successfully basic functionality on VX800, and partially successfully
on VX900 (on VX900 Xorg failed to initialize due to openchrome related issues,
viadrmums attaches and it is by used the driver).
Didn't test on VX855, I don't have one.

Pull up to netbsd-10 is needed.

RISC-V support that works on QEMU with a single hart.

Thanks for Simon Burge for plic(4).

sys/modules/Makefile: Use MACHINE_CPU, not MACHINE_ARCH, for aarch64.

This way it covers both little-endian and big-endian.

aarch64: Build drm modules.

Create compat_100 module infrastructure now that we have branched
for NetBSD-10

branches: 1.274.2;


Split the BMP280 / BME280 driver into common code and create I2C and
SPI attachments.

A driver for the Bosch BMP280 / BME280 temperature, humidity and
atmospheric pressure sensor. This is an inexpensive to moderately
expensive chip available from a large number of places. The driver
supports all aspects of the two chips, except for the repeating read
mode which would allow for sub-second queries, such as fall detection
or perhaps even as an altimeter. This driver also only supports the
I2C interface and not the SPI interface.

The BME280, the one with humidity, is not fully tested at this point,
awaiting upon a breakout board and may not show proper humidity.

A driver for the Aosong AHT20 temperature and humidity sensor. While
slow for an I2C sensor it is inexpensive and should work well enough
in most indoor conditions. All features of the chip are supported.

Move emuxki from i386/amd64 specific modules to attachment specific
modules (effectively disabling it for the build for now, as it needs
setlist fixes and breaks the build).

emuxki(4): allow building as a module

Tested on NetBSD/amd64 with a Sound Blaster Live! Value (CT4870)

Note that this required setting outputs.master to the maximum value
allowed (255) to get sound out, and then cranking the volume pretty
high.

Additional sound cards sponsored by the NetBSD Foundation; thanks!

drm: Hook up the drmkms modules to the build.

Enable amdgpu module & firmware on x86

Make it easier to test this one out, add `load amdgpu` before boot netbsd.

XXX there should probably be a drm block in sys/modules/Makefile which
includes aarch64.

drm: Modularize ttm.

Combine the midi and sequencer modules into a single midi_seq module
to avoid a circular dependency as noted in kern/56772. Retain minimal
modules of the original names to accomodate auto-loading upon access
to the /dev/xxx nodes.

Split some common stuff into scsi_subr module. This enables loading
of the iscsi module whether or not there are any scsi things built
into the kernel.

Addresses the iscsi portion of kern/56772

Create a loaable adiantum module, and make cgd require it.

This enablees use of a loadable cgd module, rather thtan requiring
it to be built-in.

Partially resolves kern/56772

Split i2c_subr.c into a separate module rather than including it in
the iic module. There are valid configurations where i2c_subr code
can be both built-in and part of a loaded module (eg, piixpm is in
the kernel, but the iic module is loaded later). This causes the
in-kernel linker to detect a duplicate symbol.

A driver and user land utility for the Sparkfun Serial Controlled Motor
Driver module as illustrated here:

https://www.sparkfun.com/products/13911

A SCMD module is a ARM SOC simular to a Arduino in front of a motor
driver chip. The single SCMD module can control two motors and up to
16 additional modules can be chained together using an internal I2C
bus. One can interface with the SCMD using tty uart commands, SPI or
I2C. The driver in this commit adds a kernel driver for the I2C and
SPI interfaces. The command line utility provides a set of
convenience commands that support most of the functions of the SCMD
and is able to use the tty uart mode, SPI user land or the included
kernel driver in a uniform manor.

The use of the SCMD module is mostly for small robots and the like,
but it can control anything that is controllable by voltage.

add support COMPAT_LINUX32 for aarch64

Driver for the Sensirion SHT30/SHT31/SHT35 temperature and humidity
sensor such as:

https://www.adafruit.com/product/2857

This is a higher priced sensor with a lot of features, including the
ability to do sub-second periodic updates. The driver supports
everything about the sensor except for the alert pin.

A driver for the Sensirion SGP40 MOx gas sensor. An example of this
chip from Adafruit is:

https://www.adafruit.com/product/4829

This is a moderately priced gas sensor that can detect volatile
organic compounds in the air. The driver uses the 3-clause BSD
licensed VOC algorithm provided by Sensirion to turn the raw sensor
metric into a VOC index which can indicate the quality of the air in a
particular indoor environment. All published functions of the chip
are supported and one unpublished feature.

Modularize compat_linux(8) for aarch64.

A driver for the Sensirion SHT40/SHT41/SHT45 temperature and humidity
sensor. An example of this chip is:

https://www.adafruit.com/product/4885

This is a lower cost chip that provides higher then usual precision
according to the data sheet. This driver supports all of the published
functions that the chip has.

Disable drmkms module builds.

They haven't been functional (and won't be before fixing genfb abi).
In a new drm update, we haven't prioritized fixing the build either.

Build and install the if_run module. run(4) is not necessarily included
in all GENERIC kernels (as reported on libera IRC).

Fix broken name

s/blake2s/blakes2s/ to match the directory that exists

modules for blake2s libsodium and if_wg

fix various typos in compatibility, mainly in comments.

Add a new link-aggregation pseudo interface named lagg(4)

- FreeBSD's lagg(4) based implementation
- MP-safe and MP-scalable

branches: 1.249.2; 1.249.4;
don't restrict pad module to i386 and amd64.

- module build tested on amiga, vax, i386, amd64, evbarm.
- build.sh release tested on i386.
- pad module functionality tested on aarch64.

branches: 1.248.2;
Separate the compat_netbsd32_coredump from the compat_netbsd32 and
coredump modules, into its own module.

Welcome to 7.99.75 !!!

branches: 1.247.2;
modularize, and fix build error

Add HAVE_NVMM and use it to control the build of NVMM related components.
Defined to "yes" on amd64, "no" everywhere else.

Added iavf(4) that is based on OpenBSD's iavf(4) implementation

reviewed by msaitoh@n.o and knakahara@n.o

remove SMBFS and nsmb(4) - kernel part

it's unmaintained and supports only obsolete SMB1

Split out the quota code from the rest of compat_netbsd32 module. This
allows loading of compat_netbsd32 on kernels that don't have ``options
QUOTA'' enabled.

Fixup the evbarm PCI modules

Disable hifn again

Group some PCI only modules together and only build them on a subset of
platforms. The list is not complete.

Make ixl(4) be able to build as a module

Retire azalia(4).

Split the compat_50 module into two, separating the QUOTA-related
stuff from the rest of the module. This allows loading of the
(main) compat_50 module on kernels that don't include ``options
QUOTA''.

Welcome to 9.99.40 !

Addresses PR kern/54875

Remove filemon(4).

Discussed on tech-kern:
https://mail-index.NetBSD.org/tech-kern/2020/01/13/msg025938.html

This was never (intentionally) enabled by default, and the design has
some shortcomings. You can get mostly the same results with ktrace,
as in usr.bin/make/filemon/filemon_ktrace.c which is now used instead
of filemon for make's meta mode.

If applications require higher performance than ktrace, or nesting
that ktrace doesn't support, we might consider adding something back
into the vfs system calls themselves, without hijacking the syscall
table. (Might want a more reliable output format too, e.g. one that
can handle newlines in file names.)

Remove the strip(4) - Starmode Radio IP - pseudo-device driver. It is
long since obsolete.

branches: 1.234.2;
Add module build for aq(4)

Revert the removal of filemon.

Retire filemon, discussed on tech-kern@.

Ported driver for Intel Ethernet 700 series

reviewed by msaitoh and knakahara

Continue to build the filemon module, but don't install it. Hopefully
this will help us detect any additional bit-rot that might occur.

XXX It might be a good idea to modify the file permissions on /dev/filemon
XXX to prevent auto-loading of the driver module by non-privileged users.

Disable filemon.

It isn't suited for general use (that is, it poses security risks),
but the existence of the module means it is auto-loaded when /dev/filemon
is opened, which can be done by any user.

Thanks Ilja van Sprundel for the heads up.

Implement a front-end driver of virtio-9p called vio9p

In conjunction with mount_9p, it enables a NetBSD system running as a VM guest
to mount an exported filesystem by the host via virtio-9p. It exports a 9p
end-point of virtio-9p via a character device file for mount_9p.

Reviewed by yamaguchi@

Add a new member to struct vfsstat and grow the unused members
The new member is caled f_mntfromlabel and it is the dkw_wname
of the corresponding wedge. This is now used by df -W to display
the mountpoint name as NAME=

enable building modules for if_aue(4), if_cdce(4), if_cue(4),
if_kue(4), if_upl(4), if_url(4), and if_urndis(4)

build exec_elf32 module on arm64.

Build an if_udav module (untested)

introduce a library of common code / backends to share code between
USB ethernet drivers.

usbnet.h introduces a new set of APIs to provide common solutions
for these driver features:
- USB endpoint pipe handling
- rx and tx chain handling
- generic handlers or support for several struct ifnet callbacks
- MII bus locking
- interrupt handling
- partial autoconf handling: much of attach, and detach/activate
can use common versions directly.

currently, only axen(4) and cdce(4) are converted. the reductions
in these drivers are quite significant: if_cdce.c is reduced from
1000 lines to 320 lines, and if_axen is reduced from 1902 lines
to 1021 lines.

add a "usbnet" module and make the if_axen module depend upon it.

branches: 1.222.2;
Split the ufs code out of the ffs module and into its own module.

Adapt chfs and ext2fs modules accordingly.

Now that the if_srt module has a chance of working (ie, it now
actually attaches/detaches the cdevsw!), add the required srt
module to allow module autoload triggered by opening /dev/srtN

XXX As noted in the recent commit to if_srt.c, someone(tm) needs
XXX to create the /dev/srt* device nodes with major 179. :)

Add a loadable module for tap(4).

The code was already modularized, we simply didn't build the loadable
module.

Note also that since the tap(4) device can be reasonably accessed by
either creating a device instance (using ifconfig(8)) or by opening
/dev/tap, we need to create both if_tap.kmod and tap.kmod (similar to
what is done with tun(4)).

Add ure(4): RealTek RTL8152/RTL8153 10/100/Gigabit USB Ethernet device.
Ported from OpenBSD. Support for RX/TX checksum offload added by myself.

don't assume _LP64 == supports COMPAT_NETBSD32.

this is not true for alpha, ia64 and arm32 ports, and the first two
were not building because of it, and the latter would be missing
the oabi support (likely not a big deal, but still wrong.)

add a makefile fragment that tells you if it is supported and include
it where needed to define COMPAT_NETBSD32 when building the normal
kernel (ie, modules & rump.)


fixes alpha build, probably fixes ia64 build.


XXX: still leaves some netbsd32 code in rf_netbsdkintf.c, that should
be moved into some hooks, but first the configuration setup
needs to be moved into a common function the netbsd32 code can
call into, vs living in the switch case itself.

Don't include the raidframe compat code in the main raid module, the
compat code lives in their own compat_raid_xx modules, which will now
be autoloaded if needed.

While here, extract the compat_netbsd32_raid code into its own module,
too.

Welcome to 8.99.34

Merge the [pgoyette-compat] branch

Build bpfjit and sljit modules on aarch64.

Remove compat_svr4 and compat_svr4_32, as discussed on tech-kern@ recently,
but also as discussed several times in the past.

Remove the rest of my local change that somehow snuck in to an
earlier commit.

Remove obsolete ksem entry to prevent build break.

Include the compat_netbsd32* modules for sparc64

Their absence was noticed by martin@ when the recent libnv-related
build failure on amd64 did not affect sparc64!

Add NVMM - for NetBSD Virtual Machine Monitor -, a kernel driver that
provides support for hardware-accelerated virtualization on NetBSD.

It is made of an MI frontend, to which MD backends can be plugged. One
MD backend is implemented, x86-SVM, for x86 AMD CPUs.

We install

/usr/include/dev/nvmm/nvmm.h
/usr/include/dev/nvmm/nvmm_ioctl.h
/usr/include/dev/nvmm/{arch}/nvmm_{arch}.h

And the kernel module. For now, the only architecture where we do that
is amd64 (arch=x86).

NVMM is not enabled by default in amd64-GENERIC, but is instead easily
modloadable.

Sent to tech-kern@ a month ago. Validated with kASan, and optimized
with tprof.

Rework PCI and AGP conditionalization.

- Push drm_pci_set_unique into driver callback.
- Eliminate drm_pci_set_unique_hook.
- Gather all drm_agp_* functions into struct drm_agp_hooks.
- Replace the nonsensical old atomic garbage by serious locking.
- Make drm_agpsupport.c its own module.
- Eliminate NDRMKMS_PCI.
- Use NAGP from "agp.h" only in drm_module.c for horrible hack.
=> See comment in file for rationale.
- Always define CONFIG_PCI=1 and CONFIG_AGP=1.
- Always go through the drm_agp_* function hooks.
- Ifdef out nouveau agp stuff that doesn't go through drm_agp_*
for reasons that I'm too frustrated to figure out tonight.
- pci_iomap no longer automagically does agp_i810_borrow.
=> Use drm_agp_borrow instead.

Add mue(4), driver for Microchip LAN75xx/LAN78xx known as internal NIC of
Raspberry Pi 3 B+, from OpenBSD.

Tested on Raspberry Pi 3 B+ (LAN7800) and Z-TEK ZE582 (LAN7500).

* BUGS/TODO

- If the media type is set to something other than 1000baseT-FDX, data
transmission becomes quite unstable. Also, ukphy(4) recognize 1000baseT as
a supported media type, but it is not in fact.

- Catch up with changes made to usmsc(4) in nick-nhusb branch, i.e.,
make the driver MP-safe.

- Support RX/VLAN/TX chekcsum offloading.

Merge the tprof_pmi and tprof_amdpmi modules into a single tprof_x86
module.

Remove viadrm(4), superseded by viadrmums.

Aside from viadrm using older drm code, it's also dysfunctional right now.
See PR port-i386/53364.

branches: 1.205.2;
add virtio_pci to list of not-yet-enabled modules

Add a 1PPS-over-GPIO driver, originally by Brad Spencer, with changes by
me to adapt to the new GPIO interrupt interface and support a wider variety
of GPIO pin configuations.

PR kern/51676

Add an example "gpioirq" driver that demonstrates interrupts on GPIO
pins. Will be enhanced in the future to support sending events to
user space on edge-triggered interrupt events.

Based on initial work by Brad Spencer.
PR kern/51676

branches: 1.202.2;
Descend into subdirectory to create the module for ichsmb(4) driver.

Remove ksem module reference

This does not exist in HEAD.

It looks like accidentally committed in:

Add new modules (for i386 and amd64 only) for the imcsmb SMBus driver.
src/sys/modules/Makefile r1.200

Add new modules (for i386 and amd64 only) for the imcsmb SMBus driver.

Create amdsmn(4) amd amdzentemp(4) modules for X86

Merge autofs support from: Tomohiro Kusumi
XXX: Does not work yet

PR/52848: Brad Spencer: Add module glue for AM2315 and SI70xx drivers

Split ip_ecn code into its own module, so it can be shared between
gif(4), stf(4), and ipsec(4). Without this, loading the if_gif
module can result in redefined global symbols if either ipsec(4) or
stf(4) but not gif(4) is built into the kernel.

Fixes PR kern/52795 (as reported by martin@ via irc).

XXX pullup to netbsd-8

Don't build the ibcs2 module on i386.

Don't build the svr4 module on i386.

Descend into SUBDIR to actually build the wsbell module.

Missed in previous commit - thanks kre@

branches: 1.192.2;
Add the modules for audio, midi, and sequencer

Modularize ualea(4).

Unclear why we have a separate xyz.ioconf for module and XYZ.ioconf
for rump component, but at least xyz_modcmd obviates the need for
xyz_component.c (though evidently the latter could have been replaced
anyway by RUMP_COMPONENT=ioconf in the rump component Makefile).

add vioscsi to the list (disabled)

add l2tp(4) L2TPv3 interface.

originally implemented by IIJ SEIL team.

branches: 1.188.2;
Create a single combined module for spkr_pcppi and spkr_audio, and
build it for all architectures.

By doing this, we can handle pcppi, audio, or both attachments with
non-built-in modules.

XXX Still to do: the module currently cannot be unloaded, and the
XXX spkr device(s) currently cannot be detached. (Really, two
XXX sides of the same problem.)

delete spkr_synth module

Create a new module for the synthesized speaker(4).

XXX Device module autoload (invoked when the /dev/speaker is opened, and
XXX no driver exists) will not find this module. On i386 and amd64, the
XXX autoload will find the spkr module (spkr0 at pcppi0) and that module
XXX will be autoloaded. For other architectures, either include the
XXX "spkr0 at audio0" in your config file, or manually load this new
XXX spkr_synth module using modload(8).

Revert to previous. Add PCPPISPEAKER flag to fix build.

Fix building of the spkr module. The module now is the synthesized speaker.
Reported by joerg@

Build the newly-created bufq_* modules

* Split sys/kern/sys_process.c into three parts:
1 - ptrace(2) syscall for native emulation
2 - common ptrace(2) syscall code (shared with compat_netbsd32)
3 - support routines that are shared with PROCFS and/or KTRACE

* Add module glue for #1 and #2. Both modules will be built-in to the
kernel if "options PTRACE" is included in the config file (this is
the default, defined in sys/conf/std).

* Mark the ptrace(2) syscall as modular in syscalls.master (generated
files will be committed shortly).

* Conditionalize all remaining portions of PTRACE code on a new kernel
option PTRACE_HOOKS.

XXX Instead of PROCFS depending on 'options PTRACE', we should probably
just add a procfs attribute to the sys/kern/sys_process.c file's
entry in files.kern, and add PROCFS to the "#if defineds" for
process_domem(). It's really confusing to have two different ways
of requiring this file.

PR kern/51514: ptrace(2) fails for 32-bit process on 64-bit kernel

Updated from the original patch in the PR by me.

Sort entries within conditional blocks

For now, disable all the newly-created ld(4) related modules. We need
to come up with a better way to handle attachment-specific modules, and
possibly a better directory structure for modules in general, as the
current mechanism doesn't scale.

Add module build infrastructure for ld and its attachments

make it possible to load nvme(4) as module to ease testing; currently somewhat
non-optimal, since it includes the ld(4) code also and hence requires the
kernel config to have 'no ld'

Add a dummy "tun" module, whose only job is to trigger an autoload of
required module "if_tun". This allows access to /dev/tunN to autload
the require interface module.

XXX There's might be a better place/name for net/tun.c

add new modules

Modularize the pppoe driver

Modularize the sppp_subr stuff so it can be shared by pppoe and lmc
drivers as they get modularized.

Add modules for strip and slip

rename the ppp module so that it autoloads.

Modularize the ppp driver, and adjust dependencies of the compressor
modules.

For now, this is still included as a built-in module in GENERIC kernels.

PR port-ia64/51261

Use exec_elf64 modules for ia64

Add and enable a new module, slcompress

This is a prerequisite to modularizing the ppp pseudo-device

branches: 1.167.2;
New module for ipl (aka ipfilter).

Create separate modules for i2c_bitbang and bpf_filter so these files
can be included in kernels which need them without also duplicating
them in other modules. Removes the duplicate symbols I found which
prevented loading i2c and bpf modules after having fixed PR 45125.

Descend into new raid module, and update sets lists.

Modularize drvctl(4)

Modularize the clockctl pseudo-device and link to the build.

Split out the SYSV IPC stuff into its own compat_netbsd32_sysvipc
module. Adjust dependencies as needed.

Merge the compat_sysv module into the sysv_ipc module - it should
never have been a separate module in the first place (my bad).

Adjust dependencies as appropriate.

Ooops, remove a local change that wasn't supposed to be committed.

Create new compat_netbsd32_mqueue module, and descend into subdir to
build it.

Descend into new compat_netbsd32_nfssrv directory for new module, and
remove netbsd32_nfssvc.c from the original compat_netbsd32 module.

Actually create the wapbl module, since it works.

Don't build compat_netbsd32 if mips64 && building mips-n32

Add the spkr module to the build.

Descend into the examples to build them all the time. (They will not
be installed, but we still want to make sure they build to avoid any
bit-rot).

Descend into subdir to actually build the new sysv_ipc module

Split the SYSV* compat code out into a separate compat_sysv module.

For monolithic kernels, both modules will be compiled as "built-ins",
while modular environments will be able to load the SYSVSEM, SYSVSHM,
and SYSVMSG code independant from the rest of compat.

This is a necessary precursor step to making the "STD" SYSV* code
into a separate module.

Tested in both monolithic and modular environments with no errors
seen.

Build compat_netbsd32.kmod for arm and mips64

Build the tco watchdog module

Enable build of viadrmums module, i386-only.

Hold off on building viadrmums module until it works.

Module for viadrmums.

Build modules for sysmon and its subcomponents

Add modularized swwdog driver.

Split hdaudio and PCI attach glue. Even though the driver was written with
this separation in mind, all of the code lived in sys/dev/pci/hdaudio. Move
common parts to sys/dev/hdaudio and PCI attach glue to sys/dev/pci.

i2c devices don't actually have a dependency on "iic" (the bus driver)
but on "i2cexec". Create an i2cexec module (i2c_exec.c) to mirror the
dependencies in files.i2c and switch device drivers to depend on "i2cexec"
module instead.

A kernel with a USB stack and no I2C controller / bus attachment would spit
out a bunch of "WARNING: module error: can't find builtin dependency `iic'"
messages at boot. This change solves that problem.

branches: 1.142.2;
dedup and add the drmkms modules

new module

branches: 1.140.2;
Revert most of rev 1.137. Build ubsec module only for i386 and amd64 and
punt on the other arches.

Changes to existing files to enable building AARCH64 userland.
evbarm64-el
This is clang only. While gcc4.8 supports aarch64, no netbsd support has
been written for aarch64 with gcc4.8.

empty() wants a variable name, not a value. This should un-break
the arm an mips arch builds which were broken by the previous
commit.

Build ubsec(4) as a module on all arches where it was obivous how to do so.
That excludes powerpc because evppc OEA is missing definitions for
PPC_INTR_IMPL and PPC_PCI_MACHDEP_IMPL.
Adjust set lists.

Compile tested for most arches only.

add HYT-221/271/939 humidity/temperature I2C sensor
extend envsys(4) framework by %rH (relative humidity)

branches: 1.135.2;
Add hifn(4) and ubsec(4) to the NOTYET section, and note that they can
be successfully built only on architectures that have PCI.

Modularize the opencrypto components and link to the build

Create modules for software crypto components.

Re-sort in alphabetic sequence.

Modularize net/zlib so it can be used by the vnd module (and, eventually,
by an opencrypto module).

Descend into ccd

Make dksubr.c into a module, and make the cgd and dm modules depend on
it.

Now that cgd is completely modularized, descend into modules/cgd to
actually create the module.

renamed luacore to luasystm

ubsec is not a MI buildable module. disable it for now.

Build and install sljit.kmod and bpfjit.kmod iff ${MKSLJIT} != "no".

Make ubsec(4) loadable as kmod.

Build a module for usmsc(4).

linke pmf(9l) to the build

link core(9l) (docs pending) to the build

link the lua(4) module to the build

Add driver for ASIX AX88178a and AX88179 Ethernet interface.
Ported from OpenBSD.

branches: 1.119.6;
normali{s,z}e

new npflog driver split out of npf_ext_log.

Add NPF "rndblock" extension to randomly drop packets (using a random function
with a percentage or modulo operation). This is a demo module, although it can
be used for packet loss simulation. Example of a procedure in npf.conf:

procedure "somedrop" {
# Drop 1.9% of the traffic
rndblock: percentage 1.9
}

adapt the cyclic module and profile dtrace provider to netbsd.
for now, just hook the cyclic callback into hardclock().

Enable bpfjit on sparc.

Build bpfjit on i386.

Add bpfjit and enable it for amd64.

Enable sljit in amd64 kernel and modules.

Implement dynamic NPF extensions interface. An extension consists of
dynamically loaded module (.so) supplementing npfctl(8) and a kernel
module. Move normalisation and logging functionality into their own
extensions. More improvements to come.

branches: 1.110.2;
Move hdaudio and hdafg modules into x86 only section for now, untill
somebody creates a "all archs with PCI" ifdef.

Build hdaudio and hdafg modules.

Add a module for uatp(4).

Move i386 and amd64 usermode configurations to their respective directories
and make the usermode kernels buildalbe under build.sh.

The resulting kernels are build and packaged correctly as are the associated
modules.

split the coda module in a device one, and a vfs one so that it works.

Actually create the if_axe module - driver was modularized a while ago.

Actually create the dbcool(4) module. Driver was modularized a while ago.

Create the module for sdtemp (driver itself was modularized some time ago)

Also kill the module build system for ksem.

branches: 1.101.2;
Add lm, lm_isa_common, lm_isa, lm_wbsio and wbsio modules to the x86 build.

Hook secmodel_extensions(9) to modules build.

branches: 1.99.2;
Add module glue for CHFS.

Build and install new in-kernel iscsi initiator kernel module and associated
binaries (iscsid, iscsictl) if MKISCSI != no. Initiator can also be built
into a kernel by adding 'pseudo-device iscsi' in kernel configuration.

Add "npf_alg_icmp" kernel module.

Build "npf" module.

branches: 1.95.2;
add & enable vmt module

Build iic(4) and gpioiic(4) as modules.

Add filemon to the modules we build.

Link the gpioow(4) and onewire(4) modules to the build and add them to the
lists.

Add Zarlink ZL10353 DVB demodulator (or as it is now know, Intel CE623x).

add mach64drm, mgadrm, r128drm, savagedrm, sisdrm, and tdfxdrm modules

gpio(4) and gpiosim(4) can now be built and used as modules. While here,
make some functions static.

pwdog is not for all platforms, build only on i386, x86_64, and sparc64

pwdog(4) is a device driver for QUANCOM Electronic PWDOG1 PCI
attached watchdog timers.

Build acpiwdrt(4) as a module on x86.

Two placeholder comments.

include cx24227, lg3303, mt2131, nxt2k, tvpll, xc3028, coram, cxdtv, and emdtv
modules in x86 build

As wmieeepc(4) was added to amd64 GENERIC, build it also as a amd64 module.

modify the dtv device api so hardware drivers can be loaded independently
of the dtv module

Add build glue for modular spdmem(4) driver, and enable it

build and install finsio module on i386 and amd64

build and install itesio module on i386 and amd64

Build v7fs module on all architecture rather than only on i386.

Build 7th Edition(V7) File System as a kernel module.

add nsclpcsio module to i386 build

A driver for HP 3D DriverGuard; a LIS3LV02DL-based accelerometer. Tested on
HP NC4400. Like aps(4), this is commented out in the GENERIC kernels.

build dtv module

build evbppc modules in 3 different flavours:

- oea (default)
- ibm4xx
- booke

this, together with earlier machine_module[] work, should allow evbppc
platforms to use modules.

Modularize hpet(4). Works nicely with the multiple bus locations.

Modularize amdtemp(4).

branches: 1.70.2;
re-enable tprof_amdpmi

Add module build glue for odcm(4).

Import the Flash and NAND subsytem code contributed by the University
of Szeged, Hungary.

The commit includes:
- Flash layer, which gives a common API to access flash devices
- NAND controller subsystem for the flash layer
- An example OMAP driver which is used on BeagleBoard or alike ARM boards

Build glue for viac7temp(4).

Add build glue for powernow(4).

Build glue for est(4).

Add build glue for coretemp(4).

Build fujbp(4), fujhk(4), and wmieeepc(4) as modules.

build padlock module on i386

fix build!

build tprof_amdpmi

branches: 1.59.2; 1.59.4;
build and install aps module on i386 and amd64

Add a dummy-driver for ACPI fans.

Add build files for acpipmtr(4) module.

some platforms don't have bus_dma, so only build these modules on x86

hook xc5k, au8522, and auvitek into build

Add asus(x) and hpqlb(4).

Build acpidalb(4), acpitz(4), acpivga(4), and aibs(4) as modules on x86.
More to come later.

Build acpiacad(4), acpibat(4), acpibut(4), acpicpu(4), acpilid(4), and
thinkpad(4) as modules on x86. More to come later.

build acpiwmi as a module on x86

build wmi drivers as modules on x86

Also build and install compat_aoutm68k.kmod and exec_aout.kmod on m68000
to make things easier. ${MACHINE_ARCH} == ${MACHINE_CPU} on m68k
so we can't use ad.m68k for a set list to exclude m68000.

Build the new swsensor(4) device and add to set lists

Build and install compat_aoutm68k.kmod and exec_aout.kmod on m68k machines.

Extract ACPIVERBOSE into a kernel module. The module can be builtin
by defining 'options ACPIVERBOSE' in the kernel config file (no change
from current behavior), or it can be loaded at boot time on those
architectures that support the boot loader's "load" command.

ACPIVERBOSE also includes code to dump acpi/wmi data.

Extract MIIVERBOSE into a kernel module. The module can be builtin
by defining 'options MIIVERBOSE' in the kernel config file (no change
from current behavior), or it can be loaded at boot time on those
architectures that support the boot loader's "load" command.

Extract SCSIVERBOSE into a kernel module. The module can be builtin
by defining 'options SCSIVERBOSE' in the kernel config file (no change
from current behavior), or it can be loaded at boot time on those
architectures that support the boot loader's "load" command.

The module is built for all architectures, whether or not SCSI or
atapi support exists.

Extract USBVERBOSE into a kernel module. The module can be builtin
by defining 'options USBVERBOSE' in the kernel config file (no change
from current behavior), or it can be loaded at boot time on those
architectures that support the boot loader's "load" command.

The module is built for all architectures, whether or not USB support
exists.

Extract the vendor/product tables and related access routines into a
separate kernel module. Update pci bus attach routine to load the
module (if available) when we're about to start scanning the bus, and
unload the module after the scan is finished.

On architectures which support loading of modules by the boot loader,
the 'pciverbose' module can be loaded and executed without needing to
rebuild the kernel. On all architectures, using 'options PCIVERBOSE'
in the kernel configuration file will create a 'builtin' module which
is functionally equivalent to previous behavior.

XXX Although not nearly as large as the vendor and product tables,
XXX the PCI class and subclass tables might also be offloaded into
XXX the module at a future time.

XXX Cardbus (and possibly other) drivers should also be modified to
XXX load the module before scanning/attaching devices.

Connect the pf module to the build.

Connect the pad(4) kernel module to the build on i386 and amd64.

branches: 1.39.2;
DTrace: add the dtrace module to the build.

branches: 1.38.2;
add bpf kmod

Fix MKBINUTILS=no builds by leaving out xldscripts.

Remove the portalfs kernel file system driver. Replace mount_portal(8)
with a version based on puffs. User functionality remains the same.

Move the kmodule linker script source into sys/modules/xldscripts. It is
not part of binutils and definitely not GPL v3.

Discussed with mrg.

Add zfs sets and needed veriables to hook zfs into the build. ZFS on i386
need still one fix othervise it should be ready for testing.

First part of secmodel cleanup and other misc. changes:

- Separate the suser part of the bsd44 secmodel into its own secmodel
and directory, pending even more cleanups. For revision history
purposes, the original location of the files was

src/sys/secmodel/bsd44/secmodel_bsd44_suser.c
src/sys/secmodel/bsd44/suser.h

- Add a man-page for secmodel_suser(9) and update the one for
secmodel_bsd44(9).

- Add a "secmodel" module class and use it. Userland program and
documentation updated.

- Manage secmodel count (nsecmodels) through the module framework.
This eliminates the need for secmodel_{,de}register() calls in
secmodel code.

- Prepare for secmodel modularization by adding relevant module bits.
The secmodels don't allow auto unload. The bsd44 secmodel depends
on the suser and securelevel secmodels. The overlay secmodel depends
on the bsd44 secmodel. As the module class is only cosmetic, and to
prevent ambiguity, the bsd44 and overlay secmodels are prefixed with
"secmodel_".

- Adapt the overlay secmodel to recent changes (mainly vnode scope).

- Stop using link-sets for the sysctl node(s) creation.

- Keep sysctl variables under nodes of their relevant secmodels. In
other words, don't create duplicates for the suser/securelevel
secmodels under the bsd44 secmodel, as the latter is merely used
for "grouping".

- For the suser and securelevel secmodels, "advertise presence" in
relevant sysctl nodes (sysctl.security.models.{suser,securelevel}).

- Get rid of the LKM preprocessor stuff.

- As secmodels are now modules, there's no need for an explicit call
to secmodel_start(); it's handled by the module framework. That
said, the module framework was adjusted to properly load secmodels
early during system startup.

- Adapt rump to changes: Instead of using empty stubs for securelevel,
simply use the suser secmodel. Also replace secmodel_start() with a
call to secmodel_suser_start().

- 5.99.20.

Testing was done on i386 ("release" build). Spearated module_init()
changes were tested on sparc and sparc64 as well by martin@ (thanks!).

Mailing list reference:

http://mail-index.netbsd.org/tech-kern/2009/09/25/msg006135.html

enable viadrm kmod for i386

Make POSIX message queues a kernel module.

Import read-only part of the NiLFS (v2) implementation for NetBSD. It has been
tested with a DEBUG+DIAGNOSTIC+LOCKDEBUG kernel. To summerise NiLFS, i'll
repeat my posting to tech-kern here:

NiLFS stands for New implementation of Logging File System; LFS done
right they claim :) It is at version 2 now and is being developed by NTT, the
Japanese telecom company and recently put into the linux source tree. See
http://www.nilfs.org. The on-disc format is not completely frozen and i expect
at least one minor revision to come in time.

The benefits of NiLFS are build-in fine-grained checkpointing, persistent
snapshots, multiple mounts and very large file and media support. Every
checkpoint can be transformed into a snapshot and v.v. It is said to perform
very well on flash media since it is not overwriting pieces apart from a
incidental update of the superblock, but that might change. It is accompanied
by a cleaner to clean up the segments and recover lost space.

My work is not a port of the linux code; its a new implementation. Porting the
code would be more work since its very linux oriented and never written to be
ported outside linux. The goal is to be fully interchangable. The code is non
intrusive to other parts of the kernel. It is also very light-weight.

The current state of the code is read-only access to both clean and dirty
NiLFS partitions. On mounting a dirty partition it rolls forward the log to
the last checkpoint. Full read-write support is however planned!

Just as the linux code, mount_nilfs allows for the `head' to be mounted
read/write and allows multiple read-only snapshots/checkpoint mounts next to
it.

By allowing the RW mount at a different snapshot for read-write it should be
possible eventually to revert back to a previous state; i.e. try to upgrade a
system and being able to revert to the exact state prior to the upgrade.

Compared to other FS's its pretty light-weight, suitable for embedded use and
on flash media. The read-only code is currently 17kb object code on
NetBSD/i386. I doubt the read-write code will surpass the 50 or 60. Compared
this to FFS being 156kb, UDF being 84 kb and NFS being 130kb. Run-time memory
usage is most likely not very different from other uses though maybe a bit
higher than FFS.

enable tprof modules.

whitespace

Convert more MACHINE tests to MACHINE_ARCH

branches: 1.26.2;
Revert previously changes. There is no cgd and ccd directory until I properly
test ccd.kmod and cgd.kmod.

Add support for the MODULAR framework to the vnd driver. Enable building of
vnd.kmod by default.

sysvbfs module

Might as well install the dm devmapper module when we install the
other parts of the LVM tools - use the same MKLVM switch, though.

PR kern/40110: null, overlay and umap modules loading -> panic (layerfs symbols not there)

Add a layerfs module.

- don't build compat_linux on alpha until sys/modules/compat_linux/Makefile
handles required MD files under sys/compat/linux/arch/alpha
- build exec_elf64 for all 64 bit arch
- use MACHINE_ARCH!="alpha" instead of MACHINE!="alpha" for exec_elf32 check

XXX we have many histrical inconsistent use of amd64 vs x86_64.

Build compat_linux and exec_elf64 for alpha.

Descend into the new modules during the build.

Rename some modules to match their vfs name.

exec_elf32 makes no sense on alpha

Rename the accept filter modules to make module name match filter name.

Make the emulations, exec formats, coredump, NFS, and the NFS server
into modules. By and large this commit:

- shuffles header files and ifdefs
- splits code out where necessary to be modular
- adds module glue for each of the components
- adds/replaces hooks for things that can be installed at runtime

Make POSIX AIO loadable as a module.

+compat_ossaudio

Allow the POSIX semaphore code to be loaded as a module.

Remove LKMs and switch to the module framework, pass 1.

Proposed on tech-kern@.

branches: 1.10.2;
Build modular fss driver.

Reviewed by: Quentin Garnier <cube@netbsd.org>

Back out dirhash kernel module for now.

Add dirhash kernel module for sharing dirhashing support with other FS
other than UDF. Its FS agnostic and could be used for any FS

Note to self: manpage needs to follow.

branches: 1.7.2;
Add of bunch of file system modules.

build and install azalia.kmod for amd64 and i386.

branches: 1.5.2; 1.5.4;
Enable cd9660 module.

Enable putter and puffs modules in build.

Build radeondrm kmod on i386.

Build drm and i915drm modules for i386 and amd64.

branches: 1.1.2; 1.1.4; 1.1.6;
Build and install modules into /kernel/modules. Each module gets a
directory for properties, blobs, etc. It's not fixed in stone and
can easily be changed if there are issues with the location/layout.

Remove port-acorn26

OK core@

acorn26 probably was not meant to use the arm32 genassym

branches: 1.4.6;
Introduce GENASSYM_CPPFLAGS for options during genassym processing.
Consistently drop assembler flags.

set GENASSYM_DIR for arm and earm

branches: 1.2.2; 1.2.4;
Don't pass assembler flags to genassym, it doesn't compile.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.14; 1.1.52; 1.1.56;
Pull in my modules code for review/test/hacking.

branches: 1.1.2;
Introduce sys/modules/Makefile.compat and hook some compat_1[36]
machdep code into the modules. kern/58346

branches: 1.8.4; 1.8.30;
Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

Turn on DIAGNOSTIC by default for modules in HEAD.

Make us sure that it should be commented out for release branches in
a similar manner to kernel configuration files.

Discussed on tech-kern.

branches: 1.6.54;
Move SYSCTL_USE_DESCR to a better place.

Include sysctl descriptions when building modules.

set default WARNS for modules to 3 -- the only one that needs < 3 now is pf

include bsd.ioconf.mk when necessary

branches: 1.2.2;
Don't hard-code ../../ so that we can handle multi-level modules (dtrace)

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.14; 1.1.18; 1.1.38;
Pull in my modules code for review/test/hacking.

branches: 1.1.4; 1.1.6; 1.1.8; 1.1.12;
Add a note:

Do not automatically install modules that would fundamentally alter system
behaviour or create a security hole, as the system may automatically load
modules.

Add WARNS=3 as needed for -Wsign-compare issues

branches: 1.1.2; 1.1.4; 1.1.18;
Add module build infrastructure for ld and its attachments

branches: 1.1.2; 1.1.4; 1.1.18;
Add module build infrastructure for ld and its attachments

Add ioconf entries to the pseudo-devices.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.32; 1.1.50;
Rename the accept filter modules to make module name match filter name.

branches: 1.1.2; 1.1.18;
Add ioconf entries to the pseudo-devices.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.2.18;
Add ioconf entries to the pseudo-devices.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.32; 1.1.50;
Rename the accept filter modules to make module name match filter name.

branches: 1.1.2; 1.1.18;
Add ioconf entries to the pseudo-devices.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.3.56;
Use ioconf for the module declarations.

branches: 1.2.2; 1.2.4;
Bump WARNS to 4.

branches: 1.1.2; 1.1.4; 1.1.6;
Add makefiles for a sample of ACPI kernel modules.

branches: 1.1.2; 1.1.4; 1.1.8;
Use ioconf for the module declarations.

Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8; 1.1.10;
Convert acpibat to use ioconf instead of homerolled config glue.

Note, config whines about things like:
files.acpi:30: attaching undefined device `apm'

I intentionally was a lazy boy and didn't include a ton of dirt to
keep the hot napalm and riot blasts in the config thread rolling ;)

tested by jruoho (thanks!)

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.4.56;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.3.2; 1.3.4;
Bump WARNS to 4.

branches: 1.2.2;
Convert acpibat to use ioconf instead of homerolled config glue.

Note, config whines about things like:
files.acpi:30: attaching undefined device `apm'

I intentionally was a lazy boy and didn't include a ton of dirt to
keep the hot napalm and riot blasts in the config thread rolling ;)

tested by jruoho (thanks!)

branches: 1.1.2; 1.1.4;
Add makefiles for a sample of ACPI kernel modules.

branches: 1.1.2; 1.1.4; 1.1.8;
Convert the ioconf files to lower case for consistency. No functional change.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.3.56;
Use ioconf for the module declarations.

branches: 1.2.2; 1.2.4;
Bump WARNS to 4.

branches: 1.1.2; 1.1.4; 1.1.6;
Add makefiles for a sample of ACPI kernel modules.

branches: 1.1.2; 1.1.4; 1.1.8;
Use ioconf for the module declarations.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.6.2; 1.6.58;
Use ioconf for the module declarations.

branches: 1.5.2; 1.5.4;
Remove DIAGNOSTIC.

Add DIAGNOSTIC.

branches: 1.3.2;
Merge T-state a.k.a. throttling support for acpicpu(4).

Remarks:

1. Native instructions are supported only on Intel. Native support for
other x86 vendors will be investigated. By assumption, AMD and others
use the I/O based approach.

2. The existing code, INTEL_ONDEMAND_CLOCKMOD, must be disabled in
order to use acpicpu(4). Otherwise fatal MSR races may occur.
Unlike with P-states, no attempt is done to disable the existing
implementation.

3. There is no rationale to export controls to user land.

4. Throttling is an artefact from the past. T-states will not be used for
power management per se. For CPU frequency management, P-states are
preferred in all circumstances. No noticeable additional power savings
were observed in various experiments. When the system has been scaled
to the highest (i.e. lowest power) P-state, it is preferable to move
from C0 to deeper C-states than it is to actively throttle the CPU.

5. But T-states need to be implemented for passive cooling via acpitz(4).
As specified by ACPI and Intel documents, these can be used as the
last line of defence against critical thermal conditions. Support
for this will be added later.

branches: 1.2.2;
Merge P-state support for acpicpu(4).

Remarks:

1. All processors (x86 or not) for which the vendor has implemented
ACPI I/O access routines are supported. Native instructions are
currently supported only for Intel's "Enhanced Speedstep". Code for
"PowerNow!" (AMD) will be merged later. Native support for VIA's
"PowerSaver" will be investigated.

2. Backwards compatibility with existing userland code is maintained.
Comparable to the case with cpu_idle(9), the ACPI CPU driver
installs alternative functions for the existing sysctl(8) controls.
The "native" behavior (if any) is restored upon detachment.

3. The dynamic nature of ACPI-provided P-states needs more investigation.
The maximum frequency induced (but not forced) by the firmware may
change dynamically. Currently, the sysctl(8) controls error out with
a value larger than the dynamic maximum. The code itself does not
however yet react to the notifications from the firmware by changing
the frequencies in-place. Presumably the system administrator should
be able to choose whether to use dynamic or static frequencies.

Add a Makefile for ACPI CPUs.

It is safe to load and unload the whole ACPI CPU -functionality at runtime.

branches: 1.2.2; 1.2.6;
Move acpicpu(4) from "acpinodebus" to "cpufeaturebus".

branches: 1.1.2;
Use ioconf for the module declarations.

Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4; 1.1.6;
Build acpidalb(4), acpitz(4), acpivga(4), and aibs(4) as modules on x86.
More to come later.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.2.2; 1.2.58;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4; 1.1.6;
Build acpidalb(4), acpitz(4), acpivga(4), and aibs(4) as modules on x86.
More to come later.

branches: 1.1.2; 1.1.4; 1.1.8;
Convert the ioconf files to lower case for consistency. No functional change.

Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4;
Add a dummy-driver for ACPI fans.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.2.2; 1.2.58;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4;
Add a dummy-driver for ACPI fans.

branches: 1.1.2; 1.1.4; 1.1.8;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.4;
acpihed(4): New driver for PNP0C33 to notify apei(4).

PNP0C33 denotes the ACPI Hardware Error Device, which exists only to
be a vector for event notifications.

PR kern/58046

branches: 1.1.4;
acpihed(4): New driver for PNP0C33 to notify apei(4).

PNP0C33 denotes the ACPI Hardware Error Device, which exists only to
be a vector for event notifications.

PR kern/58046

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.3.56;
Use ioconf for the module declarations.

branches: 1.2.2; 1.2.4;
Bump WARNS to 4.

branches: 1.1.2; 1.1.4; 1.1.6;
Add makefiles for a sample of ACPI kernel modules.

branches: 1.1.2; 1.1.4; 1.1.8;
Use ioconf for the module declarations.

Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4;
Add build files for acpipmtr(4) module.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.2.2; 1.2.58;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4;
Add build files for acpipmtr(4) module.

branches: 1.1.2; 1.1.4; 1.1.8;
Convert the ioconf files to lower case for consistency. No functional change.

Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4; 1.1.6;
Build acpidalb(4), acpitz(4), acpivga(4), and aibs(4) as modules on x86.
More to come later.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.3.2; 1.3.58;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.2.2; 1.2.4; 1.2.6;
Bump WARNS to 4.

Build acpidalb(4), acpitz(4), acpivga(4), and aibs(4) as modules on x86.
More to come later.

branches: 1.1.2; 1.1.4; 1.1.8;
Convert the ioconf files to lower case for consistency. No functional change.

Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8;
Define ioconf to create locators.h, which is now required by acpiverbose.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.4.56;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.3.2; 1.3.4; 1.3.6; 1.3.8;
Define ioconf to create locators.h, which is now required by acpiverbose.

Remove the acpiwmi(4) dump from the ACPIVERBOSE module. Instead of this
complex solution, just use aprint_debug(9) in the driver.

branches: 1.1.2;
Extract ACPIVERBOSE into a kernel module. The module can be builtin
by defining 'options ACPIVERBOSE' in the kernel config file (no change
from current behavior), or it can be loaded at boot time on those
architectures that support the boot loader's "load" command.

ACPIVERBOSE also includes code to dump acpi/wmi data.

branches: 1.1.2; 1.1.4; 1.1.8;
Convert the ioconf files to lower case for consistency. No functional change.

add now required pci.h / NPCI. (the ia64 version builds with PCI
enabled, but i guess it won't be usable.)

XXX: enable this on evbarm*? it is x86/ia64 only currently.

Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4; 1.1.6;
Build acpidalb(4), acpitz(4), acpivga(4), and aibs(4) as modules on x86.
More to come later.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.2.2; 1.2.58;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4; 1.1.6;
Build acpidalb(4), acpitz(4), acpivga(4), and aibs(4) as modules on x86.
More to come later.

branches: 1.1.2; 1.1.4; 1.1.8;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2;
acpivmgenid(4): New driver for virtual machine generation ID.

Added to amd64/ALL and i386/ALL kernel configurations, and made
available as a loadable module acpivmgenid.kmod on x86, for now.

TBD: Add to all ACPI-supporting GENERIC kernels.

PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM
fork

branches: 1.1.2;
acpivmgenid(4): New driver for virtual machine generation ID.

Added to amd64/ALL and i386/ALL kernel configurations, and made
available as a loadable module acpivmgenid.kmod on x86, for now.

TBD: Add to all ACPI-supporting GENERIC kernels.

PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM
fork

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.4; 1.1.8; 1.1.62;
add acpiwdrt module glue

branches: 1.1.4; 1.1.8;
add acpiwdrt module glue

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.3.2; 1.3.58;
Convert the homegrown module declarations to use ioconf.

branches: 1.2.2; 1.2.4; 1.2.6;
Bump WARNS to 4.

build acpiwmi as a module on x86

branches: 1.1.2; 1.1.4; 1.1.8;
Convert the homegrown module declarations to use ioconf.

Create a loaable adiantum module, and make cgd require it.

This enablees use of a loadable cgd module, rather thtan requiring
it to be built-in.

Partially resolves kern/56772

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.2; 1.1.4; 1.1.8; 1.1.20; 1.1.92;
Add of bunch of file system modules.

A driver for the Aosong AHT20 temperature and humidity sensor. While
slow for an I2C sensor it is inexpensive and should work well enough
in most indoor conditions. All features of the chip are supported.

A driver for the Aosong AHT20 temperature and humidity sensor. While
slow for an I2C sensor it is inexpensive and should work well enough
in most indoor conditions. All features of the chip are supported.

Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4; 1.1.6;
Build acpidalb(4), acpitz(4), acpivga(4), and aibs(4) as modules on x86.
More to come later.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.4.54;
Rewrite the aibs(4) driver in order to support new models. Draws from the
revision 1.6 (claudio@) of the OpenBSD's equivalent driver. Tested by mrg@.

branches: 1.3.2; 1.3.4;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.2.2; 1.2.4; 1.2.6;
Refactor slightly and bump WARNS to 4.

Build acpidalb(4), acpitz(4), acpivga(4), and aibs(4) as modules on x86.
More to come later.

branches: 1.1.2; 1.1.4; 1.1.8;
Convert the ioconf files to lower case for consistency. No functional change.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.74;
Make POSIX AIO loadable as a module.

PR/52848: Brad Spencer: Add module glue for AM2315 and SI70xx drivers

PR/52848: Brad Spencer: Add module glue for AM2315 and SI70xx drivers

avoid various seemingly bogus warnings with GCC 14.

i couldn't see any real case for any of these issues. it seems like
the "maybe uninit" checker has gotten worse.

additionally, the "dangling pointer" checker also failing.

drm: Set CONFIG_ACPI in linux/acpi.h and make it build.

Leave a little ACPI-related functionality disabled for now, like
getting EDID out of ACPI -- needs a bit more work to make this work,
and I don't have hardware to work on that.

Should help with failures of the forms:

- unable to locate a BIOS ROM
- bios: unable to locate usable image

on various machines.

use CC_WNO_MAYBE_UNINITIALIZED and fix the clang build.

apply some warning disables for GCC 12.

*possibly* the one for intel_dp.c is a real bug but it seems very
difficult to be sure (i can't seem to convince myself either way.)

amdgpu: Define CONFIG_DRM_AMD_DC to enable display core logic.

Probably resolves a host of issues with amdgpu not detecting
displays!

Noticed by rjs@.

PR kern/57059
PR kern/57325
PR kern/57452

XXX pullup-10

branches: 1.5.4;
COPTS -> CWARNFLAGS

amdgpu: add some more CWARNFLAGS to appease clang

XXX backport this change to files.amdgpu

amdgpu: don't set -mhard-float for clang

clang complains that the option has no effect and it generates hard
float instructions without the option. soft-float not really supported
on x86_64 with clang from what I can tell.

amdgpu: Sprinkle missing COPTS.amdgpu_float options.

For some reason x86 didn't need these but aarch64 does.

amdgpu: New kernel module build goo.

amdgpu: New kernel module build goo.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.2; 1.1.6;
Create amdsmn(4) amd amdzentemp(4) modules for X86

branches: 1.1.2;
Create amdsmn(4) amd amdzentemp(4) modules for X86

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.54;
Modularize amdtemp(4).

replace amdtempbus with amdnb_miscbus.
pointed out by pgoyette@

branches: 1.3.2; 1.3.6;
Apparently we need to use the attribute and not the device name as the pseudo-root.

Catch up to current reality.

Modularize amdtemp(4).

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.2; 1.1.6;
Create amdsmn(4) amd amdzentemp(4) modules for X86

branches: 1.2.2;
use the intermediate bus

Create amdsmn(4) amd amdzentemp(4) modules for X86

Add WARNS=3 as needed for -Wsign-compare issues

branches: 1.1.2; 1.1.4; 1.1.18;
Add module build infrastructure for ld and its attachments

branches: 1.1.2; 1.1.4; 1.1.18;
Add module build infrastructure for ld and its attachments

branches: 1.1.4;
apei(4): New driver for ACPI Platform Error Interfaces.

For now it is wired up only in x86 ALL kernels, and built as a module
for x86 and Arm. Once it gets a little more testing on machines with
APEI, I would like to flip it on by default.

PR kern/58046

branches: 1.1.4;
apei(4): New driver for ACPI Platform Error Interfaces.

For now it is wired up only in x86 ALL kernels, and built as a module
for x86 and Arm. Once it gets a little more testing on machines with
APEI, I would like to flip it on by default.

PR kern/58046

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.2.4; 1.2.6; 1.2.10; 1.2.36;
Rework Apple SMC attachment goo and split into multiple modules.

The four modules are apple_smc for the core functions, apple_smc_acpi
for attachment at acpi, and apple_smc_fan & apple_smc_temp for stuff
on the SMC.

Seems like there's a lot more bookkeeping necessary to maintain
children of an applesmc device implemented by loadable modules.
Maybe there's a better way I just haven't figured out yet.

First draft of drivers for the Apple System Management Controller.

Device interface derived by reading the Linux driver source code and
<http:///www.parhelia.ch/blog/statics/k3_keys.html> as of 2012-12-05.

Includes support for attaching fan and temperature sensors to sysmon.
No accelerometer yet.

Compile-tested only, based on some run-testing of experiments from
userland. Module attachment is not quite finished, so it won't work
yet.

Remove vestigial modules/apple_smc/apple_smc.ioconf.

First draft of drivers for the Apple System Management Controller.

Device interface derived by reading the Linux driver source code and
<http:///www.parhelia.ch/blog/statics/k3_keys.html> as of 2012-12-05.

Includes support for attaching fan and temperature sensors to sysmon.
No accelerometer yet.

Compile-tested only, based on some run-testing of experiments from
userland. Module attachment is not quite finished, so it won't work
yet.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.36;
Rework Apple SMC attachment goo and split into multiple modules.

The four modules are apple_smc for the core functions, apple_smc_acpi
for attachment at acpi, and apple_smc_fan & apple_smc_temp for stuff
on the SMC.

Seems like there's a lot more bookkeeping necessary to maintain
children of an applesmc device implemented by loadable modules.
Maybe there's a better way I just haven't figured out yet.

branches: 1.1.4; 1.1.6; 1.1.10;
Rework Apple SMC attachment goo and split into multiple modules.

The four modules are apple_smc for the core functions, apple_smc_acpi
for attachment at acpi, and apple_smc_fan & apple_smc_temp for stuff
on the SMC.

Seems like there's a lot more bookkeeping necessary to maintain
children of an applesmc device implemented by loadable modules.
Maybe there's a better way I just haven't figured out yet.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.36;
Rework Apple SMC attachment goo and split into multiple modules.

The four modules are apple_smc for the core functions, apple_smc_acpi
for attachment at acpi, and apple_smc_fan & apple_smc_temp for stuff
on the SMC.

Seems like there's a lot more bookkeeping necessary to maintain
children of an applesmc device implemented by loadable modules.
Maybe there's a better way I just haven't figured out yet.

branches: 1.1.4; 1.1.6; 1.1.10;
Rework Apple SMC attachment goo and split into multiple modules.

The four modules are apple_smc for the core functions, apple_smc_acpi
for attachment at acpi, and apple_smc_fan & apple_smc_temp for stuff
on the SMC.

Seems like there's a lot more bookkeeping necessary to maintain
children of an applesmc device implemented by loadable modules.
Maybe there's a better way I just haven't figured out yet.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.36;
Rework Apple SMC attachment goo and split into multiple modules.

The four modules are apple_smc for the core functions, apple_smc_acpi
for attachment at acpi, and apple_smc_fan & apple_smc_temp for stuff
on the SMC.

Seems like there's a lot more bookkeeping necessary to maintain
children of an applesmc device implemented by loadable modules.
Maybe there's a better way I just haven't figured out yet.

branches: 1.1.4; 1.1.6; 1.1.10;
Rework Apple SMC attachment goo and split into multiple modules.

The four modules are apple_smc for the core functions, apple_smc_acpi
for attachment at acpi, and apple_smc_fan & apple_smc_temp for stuff
on the SMC.

Seems like there's a lot more bookkeeping necessary to maintain
children of an applesmc device implemented by loadable modules.
Maybe there's a better way I just haven't figured out yet.

WARNS=3 is the default

branches: 1.1.6;
support building aps(4) as a module

branches: 1.1.6;
support building aps(4) as a module

build evbppc modules in 3 different flavours:

- oea (default)
- ibm4xx
- booke

this, together with earlier machine_module[] work, should allow evbppc
platforms to use modules.

Switch evbppc/ibm4xx to generic evbppc (same as oea) kernel modules.

I've confirmed that kernels similar to amd64/conf/MODULAR work fine
both on 403 and 405.

XXX
Unfortunately, we cannot immediately switch evbppc/booke to generic
kernel modules yet; it has its own intr.h implementation.

the x86 xen and non-xen modules are identical,
so remove the unneeded extra copies.
Xen kernels now use the same modules as native kernels.

Rename module directory for ibm4xx from /stand/powerpc-4xx to
/stand/powerpc-ibm4xx to match with what we set in evbppc_machdep.c:

https://nxr.netbsd.org/xref/src/sys/arch/evbppc/evbppc/evbppc_machdep.c#86

(And we use ibm4xx not 4xx for directory in sys/arch/powerpc.)

Note that we had never enabled MODULAR for ibm4xx yet; kernel with
MODULAR option was unable to build. This should be why this discrepancy
had never been found until today...

Don't build the module sets for non-pae-32bit-pv. Noted by John D. Baker
on port-i386@, thanks.

branches: 1.3.16; 1.3.18;
Add support for build mips64 kernel modules as N32

branches: 1.2.4;
Add the infrastructure for MODULAR support for Xen kernels. At
the moment, this can only load very simple modules due to missing
symbols. It is being add at this time to make pullups to the
netbsd-7 branch easier. It is not enabled by default in any kernels.

branches: 1.1.12;
build evbppc modules in 3 different flavours:

- oea (default)
- ibm4xx
- booke

this, together with earlier machine_module[] work, should allow evbppc
platforms to use modules.

build evbppc modules in 3 different flavours:

- oea (default)
- ibm4xx
- booke

this, together with earlier machine_module[] work, should allow evbppc
platforms to use modules.

branches: 1.1.2; 1.1.6; 1.1.10;
awk support scripts to generate trampolines in modules.
(adapted from previous LKM method).
<machine/asm.h> now has a KMODTRAMPOLINE macro to generate the trampoline

branches: 1.1.2; 1.1.6; 1.1.10;
awk support scripts to generate trampolines in modules.
(adapted from previous LKM method).
<machine/asm.h> now has a KMODTRAMPOLINE macro to generate the trampoline

branches: 1.2.2; 1.2.6; 1.2.10;
Keep track of undefined symbols and then use to determine whether a wrap
is required.

awk support scripts to generate trampolines in modules.
(adapted from previous LKM method).
<machine/asm.h> now has a KMODTRAMPOLINE macro to generate the trampoline

branches: 1.1.2; 1.1.18;
Latent support for ARM_HAS_LPAE.

branches: 1.1.2; 1.1.18;
Latent support for ARM_HAS_LPAE.

build evbppc modules in 3 different flavours:

- oea (default)
- ibm4xx
- booke

this, together with earlier machine_module[] work, should allow evbppc
platforms to use modules.

branches: 1.1.2; 1.1.18;
Add support for build mips64 kernel modules as N32

branches: 1.1.2; 1.1.18;
Add support for build mips64 kernel modules as N32

build evbppc modules in 3 different flavours:

- oea (default)
- ibm4xx
- booke

this, together with earlier machine_module[] work, should allow evbppc
platforms to use modules.

Include <bsd.own.mk> before using ACTIVE_CC. Fixes make errors.

branches: 1.3.26; 1.3.28;
Put GCC/GAS options under ACTIVE_CC == "gcc".

Don't set -mmultiple or -mno-string for PowerPC, the difference is too
small to really matter and it sometimes even increases the size.

branches: 1.1.12; 1.1.26;
build evbppc modules in 3 different flavours:

- oea (default)
- ibm4xx
- booke

this, together with earlier machine_module[] work, should allow evbppc
platforms to use modules.

Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4; 1.1.6;
Build asus(x) and hpqlb(4) as modules on x86.

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.2.2; 1.2.58;
Convert the ioconf files to lower case for consistency. No functional change.

branches: 1.1.2; 1.1.4; 1.1.6;
Build asus(x) and hpqlb(4) as modules on x86.

branches: 1.1.2; 1.1.4; 1.1.8;
Convert the ioconf files to lower case for consistency. No functional change.

Add WARNS=3 as needed for -Wsign-compare issues

branches: 1.1.2; 1.1.4; 1.1.18;
Add module build infrastructure for ld and its attachments

branches: 1.1.2; 1.1.4; 1.1.18;
Add module build infrastructure for ld and its attachments

WARNS=3 is the default

branches: 1.1.2; 1.1.4; 1.1.8;
add module glue for ath_hal, ath, and if_ath_pci

adapt to ${CC_WNO_IMPLICIT_FALLTHROUGH}

Use ${CC_WNO_IMPLICIT_FALLTHROUGH} instead of
the older style more complex expressions.

convert HAVE_GCC == 7 to HAVE_GCC >= 7.

apply -Wno-error=implicit-fallthrough to ar5212_xmit.c and ar5416_xmit.c.

branches: 1.4.54;
WARNS=3 is the default

branches: 1.3.2; 1.3.4; 1.3.8;
catch up to AR9285 changes

catch up to AR9280 changes

add module glue for ath_hal, ath, and if_ath_pci

branches: 1.3.2; 1.3.4; 1.3.8;
catch up to AR9285 changes

catch up to AR9280 changes

add module glue for ath_hal, ath, and if_ath_pci

branches: 1.1.2; 1.1.4; 1.1.8;
add module glue for ath_hal, ath, and if_ath_pci

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.54;
Split out ati_pcigart into a separate module so it can be shared with r128drm

Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.

branches: 1.1.6; 1.1.62;
xc5k, au8522, and auvitek modules

Merge isaki-audio2 branch, the overhaul of audio subsystem.
- Interrupt-oriented system rather than thread-oriented.
- Improve stability, quality and performance.
- Split playback and record cleanly. Improve halfduplex support.
- Many bugs are fixed including deadlocks, resource leaks, abuses, etc.
- Simplify audio filter mechanism. The encoding/channels/frequency
conversions are completely handled in the upper layer. So the hard-
ware driver only converts its hardware encoding (if necessary).
- audio_hw_if changes:
- Obsoletes query_encoding and add query_format instead.
- Obsoletes set_params and add set_format instead.
- Remove drain, setfd, mappage.
- The call sequences are changed.
- ioctl AUDIO_GETFD/SETFD, AUDIO_GETCHAN/SETCHAN are obsoleted.
- ioctl AUDIO_{QUERY,GET,SET}FORMAT are introduced.
- cleanup config attributes: au*conv and mulaw.
- All hardware drivers should follow it (I've done as much as possible).

Some file paths are changed:
- dev/audio.c -> dev/audio/audio.c (rewritten)
- dev/audiovar.h -> dev/audio/audiovar.h
- dev/audio_dai.h -> dev/audio/audio_dai.h
- dev/audio_if.h -> dev/audio/audio_if.h
- dev/audiobell.c -> dev/audio/audiobell.c
- dev/audiobellvar.h -> dev/audio/audiobellvar.h
- dev/mulaw.[ch] -> dev/audio/mulaw.[ch] + dev/audio/alaw.c

branches: 1.3.2;
Bump default value of WARNS for modules from 3 to 5, and
explicitly set WARNS for modules that fail with WARNS=5.

Also, turn on -Wno-missing-noreturn for clang for some files.

At the moment, among ~ 360 modules,
- 2 (lua and zfs) need WARNS=0
- 1 (solaris) needs WARNS=1
- 136 need WARNS=3 (mostly due to sign-compare)
- 4 need WARNS=4
- others can be compiled with WARNS=5

Discussed on tech-kern.