Update rge* comment to include soon-to-arrive preliminary support
for RTL8127

Add Realtek 8126 to comment for rge*

actually include "amd64/conf/XEN3_DOM0.local as intended

Typoed in previous commit.

PR port-xen/59438: GENERIC content can't be in GENERIC.local because of XEN3_DOM* kernels

make XEN3 configs include XEN3.local instead of GENERIC.local

The XEN device tree is not compatible with the non-XEN device tree.

This means that one can't enable in GENERIC.local many devices that are
commented out in GENERIC. E.g,

vio9p* at virtio?
i915drm* at drm?
qat* at pci? dev ? function ?
audio* at audiobus?

Switch to including XEN3.local instead of GENERIC.local to have a common
file for local XEN3 specific configuration.

See https://mail-index.netbsd.org/tech-kern/2024/08/11/msg029672.html for
the discussion.

Note that GENERIC.local was added to most arches only in February 2023:
https://mail-index.netbsd.org/source-changes/2023/02/12/msg143277.html

Addresses: PR port-xen/59438: GENERIC content can't be in GENERIC.local because
of XEN3_DOM* kernels

Should probably be pulled up to -10 and -9.

branches: 1.203.2;
Mention DKWEDGE_METHOD_TOS in several kernel config files

PR/57889: Ricardo Branco: ext2fs does not have user immutable and append
file flags, only system ones. Restrict those to the superuser. Before
the behavior was controlled by EXT2FS_SYSTEM_FLAGS. Make that behavior the
default.

Enable genfb in DOM0 kernels

igc(4): Added to kernel config files for tested platforms

I.e., aarch64, amd64, and evbppc/DHT, at the moment.

Please feel free to add to other config files, and report us back
if you find problems :)

xen/x86: Enable heartbeat checks.

Adjust _all_ cinclude of *.local files

- Ensure always at end
- Use tab rather than spaces
- Add consistent comment
"Pull in optional local configuration - always at end"

The only functional change is that a local file which tried to
override an existing setting (eg with "no foo") would have failed
in some cases before, but now will work

branches: 1.197.4;
UFS/LFS dirhash:
- Enable UFS_DIRHASH if the architecture or kernel model specific config
file can use 128MB of RAM or more.
- Remove experimental tag from UFS_DIRHASH; it's been with RUMP kernel
and by a number of NetBSD developers for years.
- Add LFS_DIRHASH if LFS was enabled.
- Be somewhat consistent with FS options order.

PR kern/56853: add a dummy acpi_md_vbios_reset variable so that we
can again enable vga at pci for Xen.
Note that this only works in BIOS mode, not UEFI mode.

Looks like we finally can enable MSI/MSI-X on Xen
Should fix PR kern/56793 and PR kern/55667

Move XEN3_DOM0 as close as possible to GENERIC.
Document why some options are disabled
Set NO_PCI_MSI_MSIX to work around crashes reported in multiple PR

Remove uscanner(4) driver

This exists for compatibility with a Linux interface which was apparently
deprecated in Linux 2.6. There are various mailing list threads going
back to 2004 where the usefulness of this driver is discussed, but
the conclusion is that scanner software has all moved to using ugen(4)
instead, and enabling this driver will not help you scan things.

branches: 1.192.4;
XEN3_DOM0: Approach GENERIC

When processed to remove comments, blank lines, normalize whitespace,
and sort/uniq (one line was previously duplicated), this file is
identical to the previous version. It has been reorganized to reduce
diffs to GENERIC, and many missing lines from GENERIC have been added
but commented out.

XEN3_DOM0: Move closer to GENERIC (NFC)

This is another step in making XEN3_DOM0 closer to GENERIC. It is
just reordering lines, adding commented out lines, and adding a few
comments. (Test-booted with no dmesg change.)

This pass is showing cases where there are substantive and likely
undesired changes (e.g., UFS_ACL is not defined in XEN3_DOM0). Often
I added them but commented them out to preserve the NFC property of
this commit. My plan is to finish the easy NFC stuff first before
addressing functional changes.

XEN3_DOM0: Move closer to GENERIC (NFC)

This commit reorders some lines, and brings in commented lines from
GENERIC to reduce the diff. It also brings in two agp lines,
commented out, and with a warning that they are intentionally omitted.

XEN3_DOM0: Fix pckbc console attachment logic

Copy PCKBD_CNATTACH_MAY_FAIL lines from GENERIC to XEN3_DOM0.

GENERIC defines PCKBD_CNATTACH_MAY_FAIL, which means that an attempt
to activate console input on pckbc will fail if there is no keyboard
present. This is a problem on semi-modern machines that have pckbc
silicon but not ports, and thus almost always have a USB keyboard
also. What I suspect are bugs in console attachment logic lead to
attempting to attach a ukbd while there already is a console keyboard,
and with DIAGNOSTIC this is (properly) fatal, so XEN3_DOM0 blows up
with a USB keyboard in current, and probably not in 9.

Live tested on a machine that previously paniced on boot.

XEN3_DOM0: Sync VERBOSE with GENERIC

Copy the *VERBOSE option block from GENERIC, and prune the scattered
verbose options in XEN3_DOM0, surely dating from a time they were
copied from an earlier GENERIC. This amounts to adding PCIVERBOSE and
SCSIVERBOSE, and the diff from GENERIC to DOM0 boots is markedly
reduced.

amd64/conf/XEN3_DOM0: Add comment

This commit merely adds a comment explaining how XEN3_DOM0 ought to
relate to GENERIC.

remove compat_ossaudio from kernel modules

this is only useful with compat_linux and gets autoloaded when
compat_linux is loaded, so there's no reason to bake it into kernels
any more.

branches: 1.185.2;
vether: Add to kernel configurations

It's only enabled if the kernel enabled bridge AND tap.
Otherwise it's commented out.

make COMPAT_LINUX option disabled by default

leave the option enabled only in amd64/i386 ALL kernels to make
sure it continues to be compilable also when included in kernel

Remove references to BRIDGE_IPF, it is now compiled in by default.

remove NO_PCI_MSI_MSIX again, enabling MSI for Xen Dom0 by default

put back NO_PCI_MSI_MSIX, need to fix MSI issues reported in PR port-xen/55285
first

remove NO_PCI_MSI_MSIX option, MSI is supported for XenPV Dom0

Remove uyap, USB YAP phone firmware loader.

And the associated ezload EZ-USB code, which is only used by uyap.
It could theoretically be used by other drivers, but none of them are
in tree.

I suspect that this device isn't in use, as phone technology has improved
a lot since 2001 when uyap(4) was added to the tree.

Proposed with no objections on netbsd-users on 13 April 2020

MULTIPROCESSOR for dom0 should be safe now. Enable it.

Disable -g, which got enabled by mistake in the bouyer-xenpvh merge

Merge the bouyer-xenpvh branch, bringing in Xen PV drivers support under HVM
guests in GENERIC.
Xen support can be disabled at runtime with
boot -c
disable hypervisor

branches: 1.175.4;
Retire azalia(4).

remove urio(4), a driver for the Rio500 MP3 player.

At this point it is highly unlikely this 1999 device still has users,
but it still comes up in the context of maxv's USB-fuzzing (and any device
could pretend to be a urio(4)), so it's best to get rid of it.

Renamed all major entries to obsolete, as was done in previous removals.

This still requires an update to sanitizers, but they're located in
"external", perhaps it should be first committed upstream?

Proposed on tech-kern a month ago.

Retire "le* at pci?" from the shipped kernel configs:
- If the config had both an le@pci and a pcn, simply remove le@pci
(pcn would match at a higher priority anyway).
- If the config had le@pci enabled, but no pcn, change le@pci to pcn.
- If the config had le@pci commented out, but no pcn, change le@pci
to pcn and leave it commented out.

The pcn driver supports more chips than le@pci and does DMA directly
to/from mbufs rather than memory copies.

Remove FDDI support.

Remove HIPPI support and the esh(4) driver that uses it. There have not
been any users of HIPPI for some time, and it is unlikely to be resurrected.

branches: 1.170.2;
add aq(4)

No USER_LDT on Xen.

xhci(4) is considered stable enough. So, remove misleading comments.

XXX
pullup to netbsd-9

branches: 1.167.2;
Use filesystems.config to reduce duplication

We reorganise definitions for XEN source support as follows:

XEN - common sources required for baseline XEN support.
XENPV - sources required for support of XEN in PV mode.
XENPVHVM - sources required for support for XEN in HVM mode.
XENPVH - sources required for support for XEN in PVH mode.

Add ure(4) to kernel config files. Also add PHY drivers where necessary.

Re-enable ixg(4) on NetBSD/xen dom0

Namespace conflicts have been resolved.

Note that driver still has an incorrect us of __asm() gnu primitives
via

#if __FreeBSD_version < 800000
...
#endif

Since __FreeBSD_version is undefined and thus equates to 0 and thus
satisfies the inequality.

Needs fixing by driver maintainer.

Summary: Disable ixg(4) until the linuxist mb() API re-definition
within the XEN amd64 dom0 build is resolved.

Detail:
The xen public headers >= 0x00030201 depend on a linuxism - a memory
barrier "API" namely mb(), rmb() and wmb(). These are made accessible
to NetBSD code via the interface
sys/external/bsd/common/include/asm/barrier.h

Currently the ixg(4) driver uses an identical API by defining them
(incorrectly) to inline assembler macro definitions in
sys/dev/pci/ixgbe/ixgbe_osdep.h

This will result in the dom0 builds failing to build due to this
redefinition of the macros. We therefore disable the driver in
NetBSD/amd64 dom0 in order to facilitate smoothly moving the XEN
kernel builds to the new XEN source level API (RELEASE-4.11.1).

The fix for this is trivial, but needs the attention of the driver
maintainer.

Make ipmi driver available to other platforms.
Add ACPI attachment.

This change modifies the mainbus(4) entry point for all x86 sub-archs
in the following way:

i) It provides a unified entry point in
x86/x86/mainbus.c:mainbus_attach()
ii) It carves out the preliminary bus attachment sequence that is
common to all sub-archs into
x86/x86/mainbus.c: x86_cpubus_attach()
iii) It consolidates the remaining pathways as internal callee
functions so that these may be called piecemeal if required. A
special usecase of this is XEN PVHVM which may need to call the
native configure path, the xen configure path, or both.
iv) It moves the driver private data structures from
i386/i386_mainbus.c to an x86/ level one. This allows for other
sub-arch's to do similar, if needed. (They do not at the moment).
v) For dom0 kernels, it enables 'acpi0 at mainbus?' and
'acpi0 at hypervisorbus'. This serves two purposes:
a) To demonstrate the possibility of dynamic configuration tree
traversal ordering changes.
b) To allow for the common acpi_check(self, "acpibus") call in
x86/mainbus.c to not barf when it is called from the dom0 attach
path. We allow for the acpi0 device to be a child of mainbus with
the changes to amd64/conf/XEN3_DOM0 and i386/conf/XEN3PAE_DOM0
without actually probing further in the code. This path will later
be pursued in a PVHVM boot codepath.

There should be no operative changes with this change. If there are,
please complain loudly.

Remove references to "lmc" in the kernel configurations.

Add mpii(4), a driver for LSI Megaraid Fusion controllers.
Ported from OpenBSD. This driver is MP-safe.
Note that the earlier fusion controllers (Megaraid 2208, codenamed Thunderbold)
are also supported by mfi(4). mpii will take precedence if both drivers
are enabled.
Tested on a
mfii0 at pci6 dev 0 function 0: "PERC H740P Adapter ", firmware 50.3.0-1512, 819
2MB cache
mfii0: interrupting at ioapic2 pin 2
scsibus0 at mfii0: 64 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 0 lun 0: <DELL, PERC H740P Adp, 5.03> disk fixed
sd0: fabricating a geometry
sd0: 99 GB, 102399 cyl, 64 head, 32 sec, 512 bytes/sect x 209714688 sectors
sd0: tagged queueing
sd1 at scsibus0 target 1 lun 0: <DELL, PERC H740P Adp, 5.03> disk fixed
sd1: fabricating a geometry
sd1: 22254 GB, 22788608 cyl, 64 head, 32 sec, 512 bytes/sect x 46671069696 sectors
sd1: fabricating a geometry

It supports bioctl(8) ioctls, as well as sensors for the BBU and logical
drives.

Sponsored by LIP6.

remove the 'wd* at umass?' for the non-standardized and rare (extinct?)
In-System Design ATA protocol over Bulk-Only devices from most kernels,
leave only in i386/amd64 ALL; it's unmaintained and likely currently broken,
lack of test hardware makes it impossible to support

Retire the 'midway' driver. Discussed on tech-net@ recently and also three
years ago, part of removing the network ATM code.

Add (commented out) mue(4) to where appropriate.
Also add MII/PHY drivers for USB NICs if missing.

Enable L2TP on all x86 configurations, not just native amd64.

Unreference IPF/PF from the x86 config files (amd64, i386, xen), and enable
NPF instead when wanted.

branches: 1.153.2;
Add acpiecdt* at acpi?.

PR port-xen/50446
With approval from bouyer@ and acceptance, sometimes grudgingly, from
others I have removed the AGP lines from the XEN3_DOM0 config. I have
left a note in the PR suggesting that if it ever gets a proper fix that
those lines can be considered for re-inclusion.

Revert changes that pinned-down i2c parent specs. The i2c subsystem
has been enhanced to make this unnecessary.

Fully specifiy the location of indirectly-configured I2C devices. In
particular, the parent spec must not be wild-carded, as doing so doesn't
work well on systems where more than one I2C bus is present.

N.B. The x86 platforms are sort of a mess, here... legacy indirect
config and ACPI direct config sort of smashed together with the
same config file directives.

branches: 1.149.2;
With the introduction of ddb.dumpstack which is enabled by default, we no longer
need to explicitly set DDB_COMMANDONENTER to run a trace.

Follow GENERIC and enable xhci(4) by default. PR port-xen/52978

Update amdzentemp(4) attachment info. Also for ALL, remove duplicate
entry for amdtemp(4).

add amdzentemp

Alternate buffer queue strategies no longer considered experimental, update
description.

Discussed on tech-kern
http://mail-index.netbsd.org/tech-kern/2018/01/21/msg023002.html

added commented out AUTOFS pseudo-device entries

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

Add dwiic, ihidev and ims

Revive commented out DISKLABEL_EI option to kernel configuration files
that contain FFS_EI option.

Add commented-out ident lines to the XEN3_DOM{0,U} kernel config files
for consistency with other config files.

OK bouyer@

clean up COMPAT_* options for native netbsd code:
- new series of files that are useful for saying "i want everything
since netbsd 1.4", etc.
- use the fact COMPAT_* options have future dependancies to remove
many redundant options.

removes about 3000 lines total across kernel configuration files.
tested about 30 random kernels in the changed list.

Pff, I forgot to revert my change in these files. I committed only the
GENERIC files, and the message was:

Revert my changes, and re-enable COMPAT_NOMID, COMPAT_09 and COMPAT_43.
Several compat options happen to be dependent on the compat_43_* functions,
the availability of which is (wrongfully) controlled with COMPAT_43. Same
for COMPAT_09.

After a careful review, and all things considered, disable compat43 by
default on amd64. The use case is limited, the potential for damage too
high, and it is safer to run a BSD4.3 binary on i386 since the kernel does
not have to go through netbsd32 - which may not correctly reproduce i386.

Register support for SD card readers with Xen DOM0 kernels

Tested on a Lenovo ThinkPad T440s (amd64)

branches: 1.135.4;
Add ixg(4). Fixes PR#52180 from Harry Waddell.

XXX pullup to netbsd-7

Disable MULTIPROCESSOR for dom0. The dom0 support code is not MP-safe
(see xen_shm_machdep.c for example, but there are probably others).

Uncomment MULTIPROCESSOR in dom0 kernels

Comment out DISKLABEL_RDB as it is too specific for general usage.
(Also add commented out that entry for GENERIC on amd64; I forgot it)

Remove commented DISKLABEL_EI for strictly little endian architectures

It will never be useful.

Add DKWEDGE_METHOD_RDB option, which is enabled for x86, commented out for
other platforms by default.

PR kern/51208
Add DISKLABEL_EI option (and also FFS_EI if missing), commented out except for
ALL on amd64 and i386.

PR/51908: Kyle Amon: Allow customization of XEN kernels via .local files.

branches: 1.127.2;
white space police

xen dom0 SMP is now bootable again.

add the 'options MULTIPROCESSOR' in respective configs, but mark them
experimental - and thus disabled by default.

Whitespace.

Add MODULAR in Xen kernels.

wildcard speaker attachments, now that we can handle many of them.

remove VAUDIOSPEAKER for now, will be done differently.

Add a synthesized pc beeper and keyboard bell for platforms with an audio
device.

Add ichsmb(4), spdmem(4) and sdtemp(4).

branches: 1.119.2;
Turn on MPROTECT on GENERIC and both MPROTECT and ASLR on XEN*

Added nvme(4) for Non-Volatile Memory Host Controller Interface devices.
Ported from OpenBSD.

Disable uscanner in all kernel configs

As discussed on current-users@, SANE uses ugen via libusb and not
uscanner, so users are not well served by having uscanner. Consensus
is that addressing how to adjust permissions for scanners should not
block restoring basic functionionality.

(Compile-tested only, but there are multiple reports of this being the
right approach.)

Add "pseudo-device iscsi" to ALL and as a commented out hint in XEN3_*

Remove KMEMSTATS.

Uncoment options IPSEC, as requested by Gary Duzan in PR port-amd64/50052

Add iwm(4).

branches: 1.112.2;
Remove unused extended attributes kernel options

As Masao Uebayashi pointed to me, UFS_EXTATTR_AUTOSTART, LFS_EXTATTR_AUTOSTART
and UFS_EXTATTR_AUTOCREATE are not used anywhere in the code. Remove them
as they have been obsolete for a long time:
UFS_EXTATTR_AUTOSTART was replaced by mount -o extattr
LFS_EXTATTR_AUTOSTART was created to match obsolete UFS_EXTATTR_AUTOSTART
UFS_EXTATTR_AUTOCREATE was replaced by sysctl vfs.ffs.extattr_autocreate

Support for UFS1 extended attributes in GENERIC and GENERIC-like kernels

This change just brings UFS1 extended attribute *support* in the kernel,
extended attributes are not enabled unless three conditions are met:
1) filesystem is UFS1 (newfs -O1)
2) .attribute/system and .attribute/user directories are created at fs root
3) filesystem is mounted with -o extattr

Some GENERIC kernels are obviously memory constrained, the extended
attributes options were not enabled for them, but just added commented out.
(kernel were considered memory constrained if QUOTA option was disabled)

Install agp_* drivers where pchb(4) is installed except INSTALL_FLOPPY.

XXX
Config around agp(4) is done in quite wrong direction.
"pchb <- (agpbus) <- agp <- agp_*"
should be:
"pchb <- (pcibus) <- agp_* <- (agpbus) <- agp"

Don't include std.ath_hal for XEN3_DOMU.

Add HDAUDIOVERBOSE

Disable BSDLABEL and MBR DKWEDGE methods again since sysinst does not work
with wedges.

Systematize (and in many cases, fix) the comments on options COMPAT_NN.

There are quite a few configs that are missing some COMPAT_NN options
in ways that don't make sense; this should probably get cleaned up
too, but for the time being I've not added or removed anything.

- Enable Wedge support for MBR/BSDLABEL where it was commented out.
- Add apple partition support where it was missing
- Add comments where missing

Add "options COMPAT_70" to all kernel configuration files that
already had "options COMPAT_60".

branches: 1.103.2;
Fix description of DIAGNOSTIC in x86 kernels.

Comment out the xhci entries.
The driver really doesn't work well enough to be generally useful.

branches: 1.101.2;
fix manual section numbering of sysctl.
thanks wiz@

Add urtw (ok'd by christos).

Add xhci device

G/C PFIL_HOOKS from the kernel configs.

branches: 1.97.2;
remove obsolete networking options

the bogus number police

remove confusing numeric locators where they are unused.

Under FAST_IPSEC, IPSEC_ESP is mandatory; GC it.

Retire OSI network stack. OK core@

Added wpi(4) to the XEN3_DOM0 kernel for both amd64 and i386
Tested on a Lenovo ThinkPad T60 2007 (amd64)

Add alc* at pci, re-sort slightly to reduce diffs from GENERIC.

Add "options COMPAT_60" to all kernel configuration files
that already had "options COMPAT_50".

Remove references to VM86 from the amd64 kernel configs.
VM86 mode isn't supported while in long mode.

Enable support for synaptics touchpads when running Xen as domain 0; helps
usability on laptops. Fixes PR port-xen/44055.

ok bouyer@ riz@

add vmt entry to GENERIC.
standardize commented pfsync and npf entries.

branches: 1.86.2;
Rename RT2500USB driver to ural(4) as it was originally in OpenBSD,
as ural(4) and ral(4) do not actually share any code.

Enable ural(4) in hpcarm WZERO3 kernel too, as it will now build.

Fixes PR#43520.

Disable azalia(4) now that hdaudio(4) was switched on

ok bouyer@

Adjust the WSDISPLAY_COMPAT_USL comment to mention wsconscfg, to at least
give a hint that its not just for third party compat. No functional change.

Add mpii(4), a driver for LSI Logic Fusion-MPT Message Passing Interface II
SAS controllers. Ported from OpenBSD.

Replace amdtempbus with amdnb_miscbus.
This allows us to have independent drivers on the same device (northbridge f3)
each coming with a certain functionality/feature.
This way we do not need to mess with amdtemp(4) to utilize other features.

P1003_1B_SEMAPHORE is no longer optional.

Also comment out ACPIVERBOSE and MPVERBOSE

Also comment out MPDEBUG

Comment out options DEBUG from Xen kernel; also comment out
makeoptions DEBUG="-g" where it was still enabled.

branches: 1.77.2;
Support CPU microcode loading via cpuctl(8).
Implemented and enabled via CPU_UCODE kernel config option
for x86 and Xen Dom0.
Tested on different AMD machines with different
CPU families.

ok wiz@ for the manpages
ok releng@
ok core@ via releng@

WABPL is no longer considered experimental (has not been for some time)
so update its comment in config files.

branches: 1.75.2;

The rnd pseudo-device is not really optional, because it is in the same
source file as the entropy-pool code itself. Move it to std. This
will be cleaned up more when I split the sources up as they should be.

This fixes build breaks on several ports. Thanks to Havard Eidnes for
pointing them out.

branches: 1.74.2;
Per existing x86 GENERIC kernels, add:
#options BUFQ_READPRIO
options BUFQ_PRIOCSCAN
to Xen kernels.

remove iic, I fixed the i2c code

Enable an iic(4) device to prevent a linker warning.

Attach amdtemp(4) at pchb(4) instead of in place of pchb(4).

Should fix PR#45268.

Enable or note aubtfwl(4) wherever ubt(4) is enabled or noted.

Add urndis(4).

many whitespace cleanup.

Enable balloon(4) for Xen kernels.

ok bouyer@; shortly discussed on port-xen@.

Large rewrite of the balloon driver. This one:

- turns balloon into a driver that attaches to xenbus(4). This allows to
disable the functionality either at compile time or boot time via
userconf(4). Driver can implement detach or pmf(9) hooks if deemed
necessary.

- keeps Cherry's locking model, but simplify it a bit. There is now
only one target value serialized inside balloon, we do not feedback
alternative value to Xenstore (clients are not expected to see its value
evolve behind their back, and can't do much about that either)

- implements min threshold; this is an admin-settable value that tells
driver to "not balloon below this threshold." This can be used by domain
to keep memory reservations, useful if activity is expected in the near
future.

- in addition to min threshold, the driver implements internally a
safeguard value (uvmexp.freemin + 1MiB), so that admin cannot
inadvertently set min to a very low value forcing domain into heavy
memory pressure and swapping.

- create the sysctl(8) kern.xen.balloon tree. 4 nodes are actually present
(values are in KiB):
- min: (rw) an admin-settable value that prevents ballooning below this
mark
- max: (ro) the maximum size for reservation, as set by xm(1) mem-max.
- current: (ro) the current reservation for domain.
- target: (rw) the targetted reservation for domain.

- fix a few limitations here and there, most notably the max_reservation
hypercall, and KiB vs pages representations at interfaces.

The driver is still turned off by default. Enabling it would need more
approval, especially from bouyer@, cherry@ and cegger@.

FWIW: tested it two days long, from amd64 dom0 (with dom0 ballooning
enabled for xend), and bunch of domUs. Did not notice anything suspicious.

XXX it still has one big limitation: it cannot hotplug memory pages in
uvm(9) if they were not present beforehand. Example: ballooning above
physmem will give more pages to domain but it won't use it to serve
allocations, unless we teach uvm(9) how to handle the extra pages.

merge the bouyer-quota2 branch. This adds a new on-disk format
to store disk quota usage and limits, integrated with ffs
metadata. Usage is checked by fsck_ffs (no more quotacheck)
and is covered by the WAPBL journal. Enabled with kernel
option QUOTA2 (added where QUOTA was enabled in kernel config files),
turned on with tunefs(8) on a per-filesystem
basis. mount_mfs(8) can also turn quotas on.

See http://mail-index.netbsd.org/tech-kern/2011/02/19/msg010025.html
for details.

Move PowerNow! to the cpufeaturebus.

Add cpufeaturebus and est(4) for Xen.

Move ENHANCED_SPEEDSTEP, or henceforth est(4), to the cpufeaturebus.

branches: 1.61.2; 1.61.4;
add ihphy

Remove unused count from pseudo-device md.

Add new et(4)/etphy(4) devices.

Enable siisata(4) in Xen dom0 kernels.

dd dm driver to XEN configs because they do not have modules working yet.
This will enable using LVM by default on XEN DOM0 hostings running NetBSD.

Change suggested by Sam Fourman.

The Xen balloon driver enables growing and shrinking
PV domains on the fly, by collaborating with UVM and the hypervisor

Sync DKWEDGE options with GENERIC

add btmagic(4) where other Bluetooth drivers are listed

Remove unused count (invariably "4") from pseudo-device fss.

branches: 1.52.2;
add uhso(4) device where appropriate
- follow the lead of other USB driver declarations wrt commented out
- (cross-)build tested all these kernels

remove aiboost(4) from GENERICs, since it cannot win in autoconf(9) over aibs(4); ok pgoyette

New wbsio(4) driver for Winbond Super I/O attachment of lm(4) on any port.

http://mail-index.netbsd.org/tech-kern/2010/02/17/msg007338.html

Reviewed by <pgoyette>, <tech-kern>.

New aibs(4) driver for ASUSTeK AI Booster (ACPI ATK0110) hardware monitor
with limit support.

http://thread.gmane.org/gmane.os.netbsd.devel.kernel/35654

Reviewed by <pgoyette>, <jruoho> and <tech-kern>.

branches: 1.48.2;
Compile in PaX support for Xen x86 kernels (dom0 and domU).

ok bouyer@. Compiled and tested by me under i386. Only compile tested for
amd64.

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

Switch on hdaudio(4)

Refer to hdaudio as 'High Definition Audio', not
'Intel High Definition Audio' as many vendors implement the HD audio spec.

hdaudio(4) is a standards-compliant driver for Intel High Definition Audio.
It will replace azalia(4) after testing.

To use, comment out azalia in your kernel configuration and uncomment the
hdaudio and hdafg lines so it reads:

# Intel High Definition Audio
hdaudio* at pci? dev ? function ?
hdafg* at hdaudiobus?

You should also:
cd /dev
sh MAKEDEV audio

Add Intel SpeedStep and AMD PowerNow! support in Xen dom0. MSR operations
are now compiled in by default.

Note that MSR support in Xen depends on its version. rdmsr() should always
succeed, but wrmsr() to certain registers can end in a NOOP. In that case,
the error will be logged (see xm dmesg).

Setting CPU frequency (SpeedStep) requires Xen 3.3 with the option
cpufreq="dom0-kernel" passed down to hypervisor during boot.

Compiled and tested for SpeedStep under i386 for XEN3_DOM0 and XEN3PAE_DOM0
by jym@. amd64 was tested by Joel Carnat.

See also http://mail-index.netbsd.org/port-xen/2009/08/02/msg005213.html .

Commit requested by bouyer@.

add age(4)

add ale(4)

catch up with i386 xen kernels:
enable cgd by default

add options COMPAT_50

add age(4) and atphy(4)

Add pciback device to XEN3 dom0 kernels

comment out NFS_BOOT_BOOTSTATIC. It will be useful when a valid set of
NFS_BOOTSTATICs are specfied.

branches: 1.35.4;
Remove softdep, pass 1. We are focused on improving journalling.

Proposed on tech-kern@.

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

Proposed on tech-kern@.

branches: 1.33.2; 1.33.4; 1.33.8;
catch up with GENERIC
- add verbose options (commented out)
- add descriptive comments
- sort them alphabetically

Add u3g entries in kernels that have ugensa as well.

jme(4), a driver for JMicron Technologies JME250 Gigabit Ethernet and
JME260 Fast Ethernet PCI Express controllers.
Written with a lot of cut-n-paste from the FreeBSD jme(4) driver.
No support for jumbo ethernet frames yet (but should come soon).
Thanks to JMicron Technologies for providing me sample boards and
documentation for this work.

Move all platforms to new dbCool driver in preparation for removal of
chip-specific drivers

Remove esl(4)

Add amdtemp(4) to Xen Dom0 kernels.

Adding iwn(4) to GENERIC

GENERIC: add auacer(4) which is already in XEN3_DOM0
XEN3_DOM0: add azalia(4) which is already in GENERIC

Enable ipmi(4) by default in GENERIC and related kernels.

Add accept filters per request from port-xen:
http://mail-index.netbsd.org/port-xen/2008/08/10/msg004087.html

pseudo-device entries were copied from sys/arch/i386/conf/GENERIC, rev. 1.904

Reduce diff to GENERIC for compat options.

Remove SYSV IPC options as they have been replaced with sysctls.

Add "options WAPBL" to Xen configs

branches: 1.20.4;
add pckbc at acpi
add pcppi at acpi

add aiboost at acpi

Disable OSI networking.

acpidalb(4): Driver for PNP0C32 Hotkeys aka "Direct Application Launch Buttons".
"awesome" jmcneill

branches: 1.16.2;
hpqlb(4): driver for HP Quick Launch buttons - found on HP Pavilion Notebooks

branches: 1.15.2;
add acpitz at acpi

branches: 1.14.2;
Add and enable lii(4) in amd64 configurations, too, as it is very likely
the hw is used on amd64-capable otherboards, although it is not confirmed
yet.

Revert for DOM0 as well at request of Christoph Egger.
I guess this bootstatic stuff is supposed to play nicely with dhcp,
but it still doesn't for me. I suspect it's due to misdetecting the bootdev.

Comment out NFS_BOOT_BOOTSTATIC. There no use having it in the default
kernel as it needs manual configuration anyway. Also, if it's enabled
but no static options given, then the kernel will happily configure the
interface as INADDY_ANY and not even try to use DHCP.

Add wscons options, pointed out by Jonathan A. Kollasch on port-xen@

Remove GENERIC.local from the repository

Make all the kernels that currently include their corresponding GENERIC.local
file use the cinclude directive instead of include. This way config(1) will
not complain if the file cannot be found.

After doing this, remove the GENERIC.local files from the repository so that
the user will not see modified files during updates, and local changes to
them cannot end up in the repository by mistake.

Discussed in tech-kern@ earlier this month. No strong objections.

branches: 1.9.2; 1.9.6;
Sync with GENERIC, add options ACPI_SCANPCI and MPBIOS_SCANPCI,
as well as commented out ACPI_ACTIVATE_DEV and ACPICA_PEDANTIC.
Should fix PR kern/37996.

amd64 kernels should use amd64 GENERIC.local.

branches: 1.7.2;
Fixed option indentation, it should be

option<space><tab>
makeoption<space><tab>

Remove systrace. Ok core@.

Add drvctl(4)

branches: 1.4.2; 1.4.4; 1.4.8;
Enable arcmsr(4).

Remove MAXPHYS=32768 (coming from a too large cut-n-paste), it's not needed
for dom0 kernels.

branches: 1.2.2; 1.2.4; 1.2.6;
Pull up the bouyer-xenamd64 branch to HEAD. This brings in amd64 support
to NetBSD/Xen, both Dom0 and DomU.

branches: 1.1.2;
file XEN3_DOM0 was initially added on branch bouyer-xenamd64.