| History log of /src/distrib/sets/lists/manhtml |
| Revision | Date | Author | Comments |
| 1.31 | 28-Aug-2025 |
wiz | install genet(4)
|
| 1.30 | 26-Jul-2025 |
martin | branches: 1.30.2;
PR 58681: add a port of the OpenBSD viogpu(4) driver written by
Joshua Stein <jcs@openbsd.org>.
Port by George Matsumura with help from Jiaxun Yang.
|
| 1.29 | 18-Jul-2025 |
christos | Fixes for openssl-3.5.1
|
| 1.28 | 31-May-2025 |
jdc | Add a manual page for apc(4), a driver for the Aurora Personality Chip
(APC) found on SPARCstation-4/5, and emulated by qemu to idle the simulator
when the CPU is idle.
|
| 1.27 | 15-Apr-2025 |
nia | Add a man page for r128fb(4)
|
| 1.26 | 15-Apr-2025 |
nia | Add a man page for machfb(4)
|
| 1.25 | 15-Apr-2025 |
nia | Add a man page for radeonfb(4)
|
| 1.24 | 03-Apr-2025 |
bouyer | Add gscan(4), a driver for USB to CAN bus adapters.
This driver supports the Geschwister Schneider USB to CAN adapter, and
clones supported by the open-source candleLight firmware.
Add gscan to evbarm GENERIC (which already supports CAN family and the
sunxican(4) driver by default), and to amd64 ALL.
|
| 1.23 | 03-Apr-2025 |
martin | add mac68k/pbbat.html
|
| 1.22 | 11-Mar-2025 |
brad | 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.
|
| 1.21 | 26-Feb-2025 |
martin | add amdgpio(4)
|
| 1.20 | 24-Feb-2025 |
martin | conditionalize efi(8) man page variants on efi_rt
|
| 1.19 | 24-Feb-2025 |
christos | new efi program
|
| 1.18 | 27-Jan-2025 |
christos | Add getnameinfo files
|
| 1.17 | 23-Jan-2025 |
brad | 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
|
| 1.16 | 20-Jan-2025 |
maya | Add ncm(4) a driver for USB Network Control Model
Seen on my Google Pixel 8, which implements ncm instead of urndis.
|
| 1.15 | 16-Dec-2024 |
brad | A driver for the MCP-2221 / 2221A multi-io chip. This is a USB to
UART / GPIO / I2C multi-io chip probably based upon a programmed PIC.
The end result is that simple gpio and i2c can exist on any system
that provides a USB port. This is everything from a RPI to a
Virtualbox VM.
o The UART presents itself as a umodem(4) device and pretty much works
as one would expect.
o There are 4 simple GPIO pins with multiple functions that attach to
gpio(4). Support for basic GPIO input and output exists with gpioctl,
the ADC, DAC and clock pulse functions exist as ALT functions. For
the ADC and DAC /dev/ devices are provided such that simple reads and
writes interact with the ADC and DAC. The IRQ function on pin GP1 and
bit banging the GPIO with gpiopps(4) and gpioow(4) are not really
supported. The short answer is that a spin lock is held while trying
to do USB transfers and that isn't allowed.
o There is a simple I2C engine that attaches to iic(4). This mostly
works as expected, except that a READ without STOP is not supported by
the engine which causes problems for some drivers. Most drivers do
not seem to use READ without STOP and seem to work as expected.
Support for changing the I2C speed is not supported, but nothing much
really does that.
o A userland utility called umcpmioctl(8) is provided that allows the
query of the status of the chip and allows for the query of the flash
memory and the setting of some of the flash memory parameters mostly
related to gpio. This utility interacts with a control device in
/dev/. The flash memory contents is copied to the sram on boot up of
the chip and can be used to adjust how the chip sets up the gpio pins,
among other things. Support for setting or entering the chip password
is not provided.
o A number of sysctls are provided to mess with various settings.
These are detailed in the man page.
While not perfect, the chip is reasonable, cheap, and has at least one
vendor making a breakout board. It is also one of the only ones in
this space that has enough documentation to write a driver.
Support for a related chip, the MCP-2210, which provides SPI and GPIO
may exist some day as the programming interface is very simular.
|
| 1.14 | 15-Dec-2024 |
mrg | install new pryo(4) manual, as requested in PR#58903.
|
| 1.13 | 07-Dec-2024 |
martin | Now that shutdown(8) provides info why we are shutting down to the
shutdown scripts, add an optional local hook /etc/rc.shutdown.final
called last in the shutdown sequence and passed the reason.
This allows for easy local integration of special UPS commands before
we power down (e.g. to restart the UPS after some delay in case
utility power is restored too early and the machine has already powered
down and will only restart when it's power input is restored after being
off for a few seconds)
|
| 1.12 | 04-Nov-2024 |
brad | 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.
|
| 1.11 | 30-Oct-2024 |
christos | Hook zstd to the build and enable it for libarchive and file.
|
| 1.10 | 20-Oct-2024 |
mlelstv | Add ietp(4) man page.
|
| 1.9 | 02-Sep-2024 |
ozaki-r | distrib, etc: install shmif_pcapin and its tests
|
| 1.8 | 26-Aug-2024 |
riastradh | 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
|
| 1.7 | 19-Aug-2024 |
riastradh | apei(4), acpihed(4): Wire up man pages to build.
PR kern/58046: Missing APEI (ACPI Platform Error Interface) support
|
| 1.6 | 18-Aug-2024 |
rin | sets/man{,html}: Add gdbserver(1)
|
| 1.5 | 01-Aug-2024 |
martin | Add new ascaudio.html
|
| 1.4 | 12-Jul-2024 |
christos | updates for OpenSSL man pages
|
| 1.3 | 04-May-2024 |
reed | branches: 1.3.2;
Install the mkcsmapper.1 and mkesdb.1 manpages.
|
| 1.2 | 30-Apr-2024 |
andvar | viac7temp(4): rewrite temperature sensor to read value from MSR instead of using
documented cpuid instruction and eax register.
This approach is adapted from linux via-cputemp.c, no official documentation is
currently available. However, msr value seems to work on all tested CPUs while
documented cpuid instruction typically reports 0, even for my C7-D CPU.
msr value seems to have temperature in Celsius in lower 24-bits without fraction
(thus "msr & 0xffffff;" is used).
Tested on my personal systems based on CPUs below (i386 and amd64):
C7-D 1.6GHz (i386 only), Nano X2 L4350E, Nano X2 U4300, U2300 Nano, KX-U6580.
Also got one response via email which was based on Nano X2 L4050 (VE-900).
Nano reports independent values for each core.
KX-U6580 seems to show the same value for all cores but more testing is needed.
Since it works on amd64 capable CPUs, adding driver to GENERIC kernel config.
Also moving viac7temp man page to x86 instead of i386 (with updates).
In theory the change should add support for all VIA Nano CPUs and Zhaoxin CPUs
at least up to KX-6000(G) series.
In the future I may need to introduce amd64 kernel module as well.
Plan to pullup to at least netbsd-10.
Patch mainly reviewed by riastradh.
|
| 1.1 | 09-Apr-2024 |
nia | Add new sets: base32, debug32, manhtml
- base32 contains (when MKCOMPAT=yes) shared libraries for 32-bit
compatibility, previously included in base
- debug32 contains (when MKCOMPAT=yes) debug symbols and static libraries
containing debug symbols for 32-bit compatiblity, previously included
in debug
- manhtml contains (when MKHTML=yes) the HTML files previously included
in 'man', which are of limited utility without third-party software.
The motivation for this change is to be able to easily exclude sets
from CD-ROM images that go over the size limit without xz compression
(which many NetBSD platforms struggle to extract at acceptable speeds).
|
| 1.3.2.2 | 02-Aug-2025 |
perseant | Sync with HEAD
|
| 1.3.2.1 | 29-Jun-2024 |
perseant | Implementation of exFAT filesystem, with compilation conditional on MKEXFATFS
make variable.
|
| 1.30.2.1 | 29-Aug-2025 |
martin | Pull up following revision(s) (requested by wiz in ticket #21):
distrib/sets/lists/man/mi: revision 1.1810
share/man/man4/Makefile: revision 1.748
share/man/man4/genet.4: revision 1.1
distrib/sets/lists/manhtml/mi: revision 1.31
share/man/man4/genet.4: revision 1.2
Add man page for genet(4)
install genet(4)
Fix name in one place.
Found by skrll
|
