kernel/fwohci: Avoid confusion with USB's OHCI_DEBUG kernel option.

fwohci's is just an internal define that enables a debug printf.

kernel: Rename the HZ kernel option to HZ_DEFAULT.

The define used by the kernel (and altered by this option) was renamed
back in 6de4cf8a045febfcb20dde5bb7a51ca13e3d33a6.

This also avoids some con

kernel: Rename the HZ kernel option to HZ_DEFAULT.

The define used by the kernel (and altered by this option) was renamed
back in 6de4cf8a045febfcb20dde5bb7a51ca13e3d33a6.

This also avoids some confusion with the drm code which uses its own
HZ define.

show more ...

kernel/pvscsi: Port pvscsi(4) over to DragonFly.

* Currently, MSI-X support is missing.

* If loaded as a module, it has to be in loader.conf. I don't know if
that is different on FreeBSD.

Report

kernel/pvscsi: Port pvscsi(4) over to DragonFly.

* Currently, MSI-X support is missing.

* If loaded as a module, it has to be in loader.conf. I don't know if
that is different on FreeBSD.

Reported-by: Georg Bege <georg@bege.email>
Tested-by: Georg Bege <georg@bege.email> (on a VPS from IONOS)
Pierre-Alain TORET <pierre-alain.toret@protonmail.com>
(on Linux Workstation Pro 17)
myself (on Windows Workstation 17 Player)

show more ...

kernel/acpi: Remove the never used ACPI_NO_SEMAPHORES kernel option.

kernel: Remove ndis(4) and associated tools and stuff.

ndis(4) was a wrapper to allow running binary Windows network
drivers that conformed to the Network Driver Interface Specification,
i.e. NDIS.

kernel: Remove ndis(4) and associated tools and stuff.

ndis(4) was a wrapper to allow running binary Windows network
drivers that conformed to the Network Driver Interface Specification,
i.e. NDIS.

It only ever supported drivers from the days of Windows XP and
Windows Server 2003 (i.e. NDIS 5.1). And even if one was actually
able to extract the .sys and .inf files from the driver package and
successfully convert them to a building module, which both were
adventures in itself, it could be any result when trying to run it,
depending on the card and driver, from resonably working to not
working, even crashing. But it did work for some cards, so it had
some limited merit in its time.

NetBSD removed it in 2018, FreeBSD in January 2021, so let's follow
suit now.

show more ...

Sync tpm(4) with FreeBSD.

Adds TPM 2.0 support, mainly.

kernel/options: Fix wrong LINT->LINT64 replacement in a comment.

kernel: Add NO_SYSCTL_DESCR option to exclude sysctl descriptions.

<sys/sysctl.h> has the code for it already, brought in in commit
8e82189d49ed5be4533e1a3d2609460e8aae81bf, but the option was not
a

kernel: Add NO_SYSCTL_DESCR option to exclude sysctl descriptions.

<sys/sysctl.h> has the code for it already, brought in in commit
8e82189d49ed5be4533e1a3d2609460e8aae81bf, but the option was not
added.

While here, remove some old no-op IPSec related options.

show more ...

sys/vfs/fuse: Add initial FUSE support

The basic code design comes from FreeBSD, but the code is written
from scratch. It was just easier to write from scratch than trying to
port sys/fs/fuse/* in F

sys/vfs/fuse: Add initial FUSE support

The basic code design comes from FreeBSD, but the code is written
from scratch. It was just easier to write from scratch than trying to
port sys/fs/fuse/* in FreeBSD for various reasons. Note that this is
to implement FUSE API/ABI, but not to be compatible with FreeBSD
implementation which contains FreeBSD specific sysctls, etc.

The initial version doesn't support FUSE_WRITE by disabling
VOP_WRITE() by returning EOPNOTSUPP. It currently works with simple
write(2) calls like dd(1) via direct I/O, but not when syncer thread
or mmap(2) gets involved under non trivial conditions. It looks to
be doable with custom VOP_GETPAGES() and VOP_PUTPAGES(), but if not
then it requires some changes to sys/kern/* and sys/vm/* to properly
support writes.

Besides above, this initial version supports basic FUSE operations
invoked from file related system calls via FUSE VOP's, but not things
like FUSE_IOCTL, FUSE_POLL, FUSE_FALLOCATE, etc. Although dmesg says
FUSE 7.28, don't expect it to support everything 7.28 (or anywhere
close to 7.28) says it has.

FUSE will be dropped from DragonFly releases until it gets stabilized
to certain extent including above, at least for write support.

show more ...

kernel: Remove puffs(4), putter(9) and associated libs and utilities.

All of these were originally pushed and hooked into the build in non-
working condition so that they would not go stale break bu

kernel: Remove puffs(4), putter(9) and associated libs and utilities.

All of these were originally pushed and hooked into the build in non-
working condition so that they would not go stale break building. The
hope was that someone would pick up the work and fix the remaining
issues, which never materialized.

This has led to more harm than good, with people occasionally assuming
that this code is functional. Also, the existence of /usr/include/fuse.h
might lead configure checks into believing that we have a working
implementation.

show more ...

kernel: Hide the sysctl.debug sysctl in the SYSCTL_DEBUG kernel option.

The output is quite excessive and was previously too easily triggered,
like with "sysctl name=value" (instead of just "name=va

kernel: Hide the sysctl.debug sysctl in the SYSCTL_DEBUG kernel option.

The output is quite excessive and was previously too easily triggered,
like with "sysctl name=value" (instead of just "name=value") in
/etc/sysctl.conf.

Taken-from: FreeBSD

show more ...

kernel: Remove the FFS_ROOT option. It was a no-op since 4.9.

kernel: Remove some old serial drivers.

Namely digi(4), rp(4) and si(4) (the latter along with its userland
utility sicontrol(8)). It is unlikely that these work properly any
more.

In preparation f

kernel: Remove some old serial drivers.

Namely digi(4), rp(4) and si(4) (the latter along with its userland
utility sicontrol(8)). It is unlikely that these work properly any
more.

In preparation for the upcoming tty_token work by dillon.

Requested-by: dillon

show more ...

kernel/drm: Remove CONFIG_PCI as a kernel option.

The code does not link in the absence of it and neither do we expect
systems without PCI support configured, nor does it make sense for
DRM specific

kernel/drm: Remove CONFIG_PCI as a kernel option.

The code does not link in the absence of it and neither do we expect
systems without PCI support configured, nor does it make sense for
DRM specific stuff in particular, so just set it unconditionally.

If anything, it could be tied to NPCI being >0 (to check if
"device pci" is in the kernel), but for that it would have to
actually build/link without CONFIG_PCI in the first place.

show more ...

drm: Add CONFIG_PCI

x86_64/lapic: Use function pointer for EOI.

This helps upcoming X2APIC support and virtualization EOI optmization,
e.g. Hyper-V can be configured to do auto-EOI.

Discussed-with: Imre Vadasz

Remove IPsec and related code from the system.

It was unmaintained ever since we inherited it from FreeBSD 4.8.

In fact, we had two implementations from that time: IPSEC and FAST_IPSEC.
FAST_IPSEC

Remove IPsec and related code from the system.

It was unmaintained ever since we inherited it from FreeBSD 4.8.

In fact, we had two implementations from that time: IPSEC and FAST_IPSEC.
FAST_IPSEC is the implementation to which FreeBSD has moved since, but
it didn't even build in DragonFly.

Fixes for dports have been committed to DeltaPorts.

Requested-by: dillon
Dports-testing-and-fixing: zrj

show more ...

kernel: Disable TCP_SIGNATURE in preparation for removing IPSEC.

Keep the code around until it gets fixed at a later date.

Requested-by: sephe

kernel/nata: Allow disabling complicated chipset drivers.

There is no point for ATA_NO_ATI option (ati chipset setup relies on sii).
Using ATA_NO_AHCI will automatically disable these ata chipset dr

kernel/nata: Allow disabling complicated chipset drivers.

There is no point for ATA_NO_ATI option (ati chipset setup relies on sii).
Using ATA_NO_AHCI will automatically disable these ata chipset drivers:
intel, marvel, nvidia, promise, siliconimage, sis, via

Only for development until nata(4) gets updated.

show more ...

i386 removal, part 66/x: Remove SND_PCM_64 as an explicit kernel option.

It only made sense as an option on i386. On x86_64 (or better, if long
is 64 bits wide) it is the default, per sys/dev/sound/

i386 removal, part 66/x: Remove SND_PCM_64 as an explicit kernel option.

It only made sense as an option on i386. On x86_64 (or better, if long
is 64 bits wide) it is the default, per sys/dev/sound/pcm/pcm.h.

show more ...

kernel: Remove some references to i386.

While there, adjust some outdated paths in comments and some minor cleanup.

kernel - Bring in evdev from FreeBSD

* This is a port of evdev, the generic input event interface, from
FreeBSD. Wikipedia: "Evdev generalizes raw input events from device
drivers and makes them

kernel - Bring in evdev from FreeBSD

* This is a port of evdev, the generic input event interface, from
FreeBSD. Wikipedia: "Evdev generalizes raw input events from device
drivers and makes them available through character devices in the
/dev/input/ directory."

* It is currently considered experimental since in rare cases it may cause
kernel crash when a device, e.g. usb mouse or keyboard, is detached
while a userland program reading from the corresponding input/eventX
device.

* In order to enable evdev, kernel needs to be rebuilt with 'device evdev'
and 'options EVDEV_SUPPORT'. For debugging, add 'options EVDEV_DEBUG'.

* At present, only ums, kbd and kbdmux can send events to their respective
input/eventX devices. More drivers will be added in due course. The sysctl
kern.evdev.rcpt_mask determines which drivers send events to evdev.

show more ...

Remove various former kernel config options for good.

kernel: Remove old SHOW_BUSYBUFS kernel configuration option.

It was removed in 5e13112632fcc46beba13acf879e178aba56391c.

Fix some trailing whitespace in sys/conf and sys/config.

Submitted-by: zrj