Changes in majors

Changes in majors http://nxr.netbsd.org/rss/src/sys/conf/majors en Copyright 2005 Java 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. /src/sys/conf/majors - 1.105 Tue Mar 11 13:56:46 UTC 2025 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. /src/sys/conf/majors - 1.104 Mon Dec 16 16:37:38 UTC 2024 brad branches: 1.103.6; gpioirq(4) version 2 This update makes this driver more than just an example and allows for: o More than one pin to be attached to a gpioirq instance. That is, the mask parameter can be greater than 0x01 now. o A /dev/gpioirqN device that allows GPIO pin interrupts to be transported into userland. This is a device that can be opened for reading with a simple fixed output indicating the device unit, pin number and current pin state. This update was used as part of a physical intrusion detection system where multiple switches (i.e. window magnetic reed switches and etc.) are tied to a bunch of GPIO inputs with userland software that reacts to the pins changing state. /src/sys/conf/majors - 1.103 Mon Nov 06 00:35:05 UTC 2023 brad branches: 1.102.4; viocon(4): New virtio tty driver imported from OpenBSD. viocon* at virtio? /dev/ttyVI?? Tested under qemu with: qemu-system-aarch64 ... \ -device virtio-serial \ -chardev socket,path=/tmp/ttyVI00,server=on,wait=off,id=ttyVI00 \ -device virtconsole,chardev=ttyVI00,name=org.NetBSD.dev.ttyVI00 \ ... I updated MAKEDEV.conf to create /dev/ttyVI?? on all ports where it looks likely to work based on: (a) having pci or a non-pci virtio attachment, (b) `qemu-system-$ARCH -M ?' mentioned something resembling the port, and (c) `qemu-system-$ARCH -device virtio-serial' launched without complaining about the virtio-serial device. (Criterion (c) excluded sparc and sparc64.) /src/sys/conf/majors - 1.102 Fri Aug 12 11:15:42 UTC 2022 riastradh 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. /src/sys/conf/majors - 1.101 Tue Dec 07 17:39:54 UTC 2021 brad 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. /src/sys/conf/majors - 1.100 Sat Nov 06 13:34:39 UTC 2021 brad efi: Add /dev/efi character device Introduce a /dev/efi character device that provides a means for accessing UEFI RT variable services from userland. Compatible with the FreeBSD ioctl interface for ease of porting their libefivar and associated tools. The ioctl interface is defined in sys/efiio.h. To enable support for this on an arch, the kernel needs `pseudo-device efi` and the MD EFI implementation needs to register its backend by calling efi_ops_register(). This commit includes an implementation for Arm. /src/sys/conf/majors - 1.99 Sun Oct 10 13:03:09 UTC 2021 jmcneill smbios: Add character device for accessing SMBIOS tables The /dev/smbios character device gives an aperture into physical memory that allows read-only access to the SMBIOS header and tables. /src/sys/conf/majors - 1.98 Sat Jul 24 11:39:19 UTC 2021 jmcneill branches: 1.97.4; acpi: add character device for accessing ACPI tables The /dev/acpi character device gives an aperture into physical memory that allows only read access to known ACPI tables: RSDP, XSDT/RSDT, and the root tables. Adapt acpidump(8) to use this interface by default, falling back to the old /dev/mem method if it is not available or if ACPIDUMP_USE_DEVMEM=1 is set in the environment. The user visible benefit of this change is that "options INSECURE" is no longer required to dump ACPI tables. /src/sys/conf/majors - 1.97 Sun Dec 06 02:57:30 UTC 2020 jmcneill branches: 1.96.2; Nix trailing whitespace. /src/sys/conf/majors - 1.96 Fri Aug 28 14:58:25 UTC 2020 riastradh Add driver for Intel XMM7360 LTE modem, based upon Linux driver available at https://github.com/xmm7360/xmm7360-pci This version works on Linux, OpenBSD, and NetBSD. OpenBSD port written for genua GmbH Modem requires python script from the master site to initialize the network, it will be added to pkgsrc shortly /src/sys/conf/majors - 1.95 Sun Jul 26 14:51:18 UTC 2020 jdolecek Add fault(4). /src/sys/conf/majors - 1.94 Sun Jun 07 09:45:19 UTC 2020 maxv 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.) /src/sys/conf/majors - 1.93 Sun Jan 19 20:41:18 UTC 2020 riastradh branches: 1.92.2; Revert the removal of filemon. /src/sys/conf/majors - 1.92 Mon Dec 23 06:45:37 UTC 2019 maxv Retire filemon, discussed on tech-kern@. /src/sys/conf/majors - 1.91 Wed Dec 18 07:37:18 UTC 2019 maxv 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@ /src/sys/conf/majors - 1.90 Mon Oct 28 02:56:40 UTC 2019 ozaki-r Wrong major. /src/sys/conf/majors - 1.89 Sun Sep 15 11:45:47 UTC 2019 maxv Add vHCI, a driver which allows to send and receive USB packets directly from userland via /dev/vhci. Using this, it becomes possible to test and fuzz the USB stack and all the USB drivers without having the associated hardware. The vHCI device has four ports independently addressable. For each xfer on each port, we create two packets: a setup packet (which indicates mostly the type of request) and a data packet (which contains the raw data). These packets are processed by read and write operations on /dev/vhci: userland poll-reads it to fetch usb_device_request_t structures, and dispatches the requests depending on bRequest and bmRequestType. A few ioctls are available: VHCI_IOC_GET_INFO - Get the current status VHCI_IOC_SET_PORT - Choose a vHCI port VHCI_IOC_USB_ATTACH - Attach a USB device on the current port VHCI_IOC_USB_DETACH - Detach the USB device on the current port vHCI has already allowed me to automatically find several bugs in the USB stack and its drivers. /src/sys/conf/majors - 1.88 Sat Sep 14 06:57:52 UTC 2019 maxv Add experimental userland interface to IPMI driver. Currently, transactions (like sensor readout) are locked, so that a userland program may interfere with envsys operation. To use this you need a program like ipmitool built with OpenIPMI support. /src/sys/conf/majors - 1.87 Sat May 18 08:38:00 UTC 2019 mlelstv Now the real number for ipmi /src/sys/conf/majors - 1.86 Sun May 05 17:24:00 UTC 2019 mlelstv