src-test2/sys/dev/uart/uart_core.c, branch release/5.4.0_cvs

This commit was manufactured by cvs2svn to create tag

2005-05-07T17:51:10Z

'RELENG_5_4_0_RELEASE'. This commit was manufactured to restore the state of the 5.4-RELEASE image.

MFC: 1.13

2005-03-31T21:55:39Z

- Allocate the interrupt resource as RF_SHAREABLE allowing uart(4) to work with shared IRQs in case the bus code, MD interrupt code, etc. permits. Together with sys/sparc64/sparc64/intr_machdep.c rev. 1.21 (MFC'ed in rev. 1.19.2.1) this fixes an endless loop in uart_intr() when using the second NS16550 on the ISA bus of sparc64 machines. - Destroy the hardware mutex on detach and in case attaching fails. Approved by: re (kensmith, scottl)

MFC: /- and my license changes for sys/[a-d]

2005-01-30T01:00:13Z

MFC uart_bus.h:1.8, uart_core.c:1.11

2004-11-20T04:07:08Z

Add UART_IOCTL_BAUD to allow us to query the hardware about the current baudrate setting.

Update for the KDB framework:

2004-07-10T21:16:01Z

o Call kdb_enter() instead of breakpoint(). o Call kdb_alt_break() instead of db_alt_break(). o Make debugging code conditional upon KDB instead of DDB.

When the interrupt cannot be INTR_FAST, it still is INTR_MPSAFE.

2004-05-04T05:54:02Z

Mark it as such.

Convert callers to the new bus_alloc_resource_any(9) API.

2004-03-17T17:50:55Z

Submitted by: Mark Santcroos Reviewed by: imp, dfr, bde

Revert the introduction of iobase in struct uart_bas. Both the SAB82532

2003-09-26T05:14:56Z

and the Z8530 drivers used the I/O address as a quick and dirty way to determine which channel they operated on, but formalizing this by introducing iobase is not a solution. How for example would a driver know which channel it controls for a multi-channel UART that only has a single I/O range? Instead, add an explicit field, called chan, to struct uart_bas that holds the channel within a device, or 0 otherwise. The chan field is initialized 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 rather large commit. Remove the use of iobase in uart_cpu_eqres() for pc98. It is expected that platforms have the capability to compare tag and handle pairs for equality; as to determine whether two pairs access the same device or not. The use of iobase for pc98 makes it impossible to formalize this and turn it into a real newbus function later. This commit reverts uart_cpu_eqres() for pc98 to an unimplemented function. It has to be reimplemented using only the tag and handle fields in struct uart_bas. Rewrite the SAB82532 and Z8530 drivers to use the chan field in struct uart_bas. Remove the IS_CHANNEL_A and IS_CHANNEL_B macros. We don't need to abstract anything anymore. Discussed with: nyan Tested on: i386, ia64, sparc64

Initialize iobase, bsh and bst.

2003-09-23T09:55:21Z

- Keep the base address in struct uart_bas for sab82532 and z8530 modules.

2003-09-23T09:25:38Z

- Remove buggy uart_cpu_busaddr() function.