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.43.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

xen/x86: Enable heartbeat checks.

i386/XEN3PAE_DOM0: Pass -g to build debug data like GENERIC.

Needed for CTF data by dtrace when MKDEBUG=no MKDEBUGKERNEL=no.

XXX pullup-10

i386/XEN3PAE_DOM0: Enable KDTRACE_HOOKS.

XXX pullup-10

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.36.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.

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.34.4;
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.33.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

remove commented out __XEN_INTERFACE_VERSION__ option, it comes via std.xen

move xen/conf/std.xen to i386/conf/std.xen, it's i386-specific

split off __XEN_INTERFACE_VERSION__ to new xen/conf/std.xenversion
and use from both i386/conf/std.xen and amd64/conf/stf.xen, so that
there is single place for the definition

branches: 1.21.2;
remove 'file-system SMBFS' and 'pseudo-device nsmb' from all kernel configs
to prepare for their eventual removal

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.

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

branches: 1.15.2;
No USER_LDT on Xen.

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

XXX
pullup to netbsd-9

branches: 1.13.4;
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.

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.

Retire the non-PAE-i386-PV configuration files. Keep only PAE-i386-PV.
Non-PAE has been dropped years ago by Xen.

The content of XEN3_* is merged into XEN3PAE_*, with "options PAE" set.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8; 1.1.14; 1.1.72; 1.1.74;
Add kernel config file for i386PAE dom0 kernel.