en Copyright 2015 Java http://172.16.0.5:8080/history/freebsd-12.1/sys/dev/uart/uart_bus_puc.c#381388b9 add snps IP uart support / genaralize UARTThis is an amalgam of a patch by Doug Ambrisko togeneralize uart_acpi_find_device, imp moving theACPI table to uart_dev_ns8250.c and advice by jhbto work around a bug in the EPYC 3151 BIOS(the BIOS incorrectly marks the serial ports asdisabled)Reviewed by: impMFC after: 8 weeksDifferential Revision: https://reviews.freebsd.org/D16432 List of files: /freebsd-12.1/sys/dev/uart/uart_bus_puc.c Sun, 19 Aug 2018 21:10:21 +0000 Matt Macy <mmacy@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-12.1/sys/dev/uart/uart_bus_puc.c#718cf2cc sys/dev: further adoption of SPDX licensing ID tags.Mainly focus on files that use BSD 2-Clause license, however the tool Iwas using misidentified many licenses so this was mostly a manual - errorprone - task.The Software Package Data Exchange (SPDX) group provides a specificationto make it easier for automated tools to detect and summarize well knownopensource licenses. We are gradually adopting the specification, notingthat the tags are considered only advisory and do not, in any way,superceed or replace the license texts. List of files: /freebsd-12.1/sys/dev/uart/uart_bus_puc.c Mon, 27 Nov 2017 14:52:40 +0000 Pedro F. Giffuni <pfg@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-12.1/sys/dev/uart/uart_bus_puc.c#c214a270 Allow setting access-width for UART registers.This is required for FDT's standard "reg-io-width" property(similar to "reg-shift" property) found in many DTS files.This fixes operation on Altera Arria 10 SOC Development Kit,where standard ns8250 uart allows 4-byte access only.Reviewed by: kan, marcelSponsored by: DARPA, AFRLDifferential Revision: https://reviews.freebsd.org/D9785 List of files: /freebsd-12.1/sys/dev/uart/uart_bus_puc.c Mon, 27 Feb 2017 20:08:42 +0000 Ruslan Bukin <br@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-12.1/sys/dev/uart/uart_bus_puc.c#64220a7e Rewrite of puc(4). Significant changes are:o Properly use rman(9) to manage resources. This eliminates the need to puc-specific hacks to rman. It also allows devinfo(8) to be used to find out the specific assignment of resources to serial/parallel ports.o Compress the PCI device "database" by optimizing for the common case and to use a procedural interface to handle the exceptions. The procedural interface also generalizes the need to setup the hardware (program chipsets, program clock frequencies).o Eliminate the need for PUC_FASTINTR. Serdev devices are fast by default and non-serdev devices are handled by the bus.o Use the serdev I/F to collect interrupt status and to handle interrupts across ports in priority order.o Sync the PCI device configuration to include devices found in NetBSD and not yet merged to FreeBSD.o Add support for Quatech 2, 4 and 8 port UARTs.o Add support for a couple dozen Timedia serial cards as found in Linux. List of files: /freebsd-12.1/sys/dev/uart/uart_bus_puc.c Fri, 28 Apr 2006 21:21:53 +0000 Marcel Moolenaar <marcel@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-12.1/sys/dev/uart/uart_bus_puc.c#875f70db Revert the introduction of iobase in struct uart_bas. Both the SAB82532and the Z8530 drivers used the I/O address as a quick and dirty way todetermine which channel they operated on, but formalizing this byintroducing iobase is not a solution. How for example would a driverknow which channel it controls for a multi-channel UART that only has asingle I/O range?Instead, add an explicit field, called chan, to struct uart_bas thatholds the channel within a device, or 0 otherwise. The chan field isinitialized both by the system device probing (i.e. a system console)or it is passed down to uart_bus_probe() by any of the bus front-ends.As such, it impacts all platforms and bus drivers and makes it a ratherlarge commit.Remove the use of iobase in uart_cpu_eqres() for pc98. It is expectedthat platforms have the capability to compare tag and handle pairs forequality; as to determine whether two pairs access the same device ornot. The use of iobase for pc98 makes it impossible to formalize thisand turn it into a real newbus function later. This commit revertsuart_cpu_eqres() for pc98 to an unimplemented function. It has to bereimplemented using only the tag and handle fields in struct uart_bas.Rewrite the SAB82532 and Z8530 drivers to use the chan field in structuart_bas. Remove the IS_CHANNEL_A and IS_CHANNEL_B macros. We don'tneed to abstract anything anymore.Discussed with: nyanTested on: i386, ia64, sparc64 List of files: /freebsd-12.1/sys/dev/uart/uart_bus_puc.c Fri, 26 Sep 2003 05:14:56 +0000 Marcel Moolenaar <marcel@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-12.1/sys/dev/uart/uart_bus_puc.c#27d5dc18 The uart(4) driver is an universal driver for various UART hardware.It improves on sio(4) in the following areas:o Fully newbusified to allow for memory mapped I/O. This is a must for ia64 and sparc64,o Machine dependent code to take full advantage of machine and firm- ware specific ways to define serial consoles and/or debug ports.o Hardware abstraction layer to allow the driver to be used with various UARTs, such as the well-known ns8250 family of UARTs, the Siemens sab82532 or the Zilog Z8530. This is especially important for pc98 and sparc64 where it's common to have different UARTs,o The notion of system devices to unkludge low-level consoles and remote gdb ports and provides the mechanics necessary to support the keyboard on sparc64 (which is UART based).o The notion of a kernel interface so that a UART can be tied to something other than the well-known TTY interface. This is needed on sparc64 to present the user with a device and ioctl handling suitable for a keyboard, but also allows us to cleanly hide an UART when used as a debug port.Following is a list of features and bugs/flaws specific to the ns8250family of UARTs as compared to their support in sio(4):o The uart(4) driver determines the FIFO size and automaticly takes advantages of larger FIFOs and/or additional features. Note that since I don't have sufficient access to 16[679]5x UARTs, hardware flow control has not been enabled. This is almost trivial to do, provided one can test. The downside of this is that broken UARTs are more likely to not work correctly with uart(4). The need for tunables or knobs may be large enough to warrant their creation.o The uart(4) driver does not share the same bumpy history as sio(4) and will therefore not provide the necessary hooks, tweaks, quirks or work-arounds to deal with once common hardware. To that extend, uart(4) supports a subset of the UARTs that sio(4) supports. The question before us is whether the subset is sufficient for current hardware.o There is no support for multiport UARTs in uart(4). The decision behind this is that uart(4) deals with one EIA RS232-C interface. Packaging of multiple interfaces in a single chip or on a single expansion board is beyond the scope of uart(4) and is now mostly left for puc(4) to deal with. Lack of hardware made it impossible to actually implement such a dependency other than is present for the dual channel SAB82532 and Z8350 SCCs.The current list of missing features is:o No configuration capabilities. A set of tunables and sysctls is being worked out. There are likely not going to be any or much compile-time knobs. Such configuration does not fit well with current hardware.o No support for the PPS API. This is partly dependent on the ability to configure uart(4) and partly dependent on having sufficient information to implement it properly.As usual, the manpage is present but lacks the attention thesoftware has gotten. List of files: /freebsd-12.1/sys/dev/uart/uart_bus_puc.c Sat, 06 Sep 2003 23:13:47 +0000 Marcel Moolenaar <marcel@FreeBSD.org>