Copy releng/7.3 to release/7.3.0 to mark 7.3-RELEASE.

2010-03-21T01:30:13Z

Approved by: re (implicit) This commit was manufactured to restore the state of the 7.3-RELEASE image.

Properly propagate overrun conditions to the TTY layer.

2006-07-27T00:07:10Z

MFC after: 3 days

Convert to new console api

2006-05-26T13:54:27Z

Don't open if we're going away.

2006-03-30T03:26:52Z

MFp4:

2006-02-24T02:42:26Z

Stop using our local UART_IPEND_* and instead use the global SER_INT_* as defined in .

- Use swi_remove() to teardown swi handlers rather than

2005-10-26T15:52:16Z

intr_event_remove_handler(). - Remove tty: prefix from a couple of swi handler names.

Reorganize the interrupt handling code a bit to make a few things cleaner

2005-10-25T19:48:48Z

and increase flexibility to allow various different approaches to be tried in the future. - Split struct ithd up into two pieces. struct intr_event holds the list of interrupt handlers associated with interrupt sources. struct intr_thread contains the data relative to an interrupt thread. Currently we still provide a 1:1 relationship of events to threads with the exception that events only have an associated thread if there is at least one threaded interrupt handler attached to the event. This means that on x86 we no longer have 4 bazillion interrupt threads with no handlers. It also means that interrupt events with only INTR_FAST handlers no longer have an associated thread either. - Renamed struct intrhand to struct intr_handler to follow the struct intr_foo naming convention. This did require renaming the powerpc MD struct intr_handler to struct ppc_intr_handler. - INTR_FAST no longer implies INTR_EXCL on all architectures except for powerpc. This means that multiple INTR_FAST handlers can attach to the same interrupt and that INTR_FAST and non-INTR_FAST handlers can attach to the same interrupt. Sharing INTR_FAST handlers may not always be desirable, but having sio(4) and uhci(4) fight over an IRQ isn't fun either. Drivers can always still use INTR_EXCL to ask for an interrupt exclusively. The way this sharing works is that when an interrupt comes in, all the INTR_FAST handlers are executed first, and if any threaded handlers exist, the interrupt thread is scheduled afterwards. This type of layout also makes it possible to investigate using interrupt filters ala OS X where the filter determines whether or not its companion threaded handler should run. - Aside from the INTR_FAST changes above, the impact on MD interrupt code is mostly just 's/ithread/intr_event/'. - A new MI ddb command 'show intrs' walks the list of interrupt events dumping their state. It also has a '/v' verbose switch which dumps info about all of the handlers attached to each event. - We currently don't destroy an interrupt thread when the last threaded handler is removed because it would suck for things like ppbus(8)'s braindead behavior. The code is present, though, it is just under #if 0 for now. - Move the code to actually execute the threaded handlers for an interrrupt event into a separate function so that ithread_loop() becomes more readable. Previously this code was all in the middle of ithread_loop() and indented halfway across the screen. - Made struct intr_thread private to kern_intr.c and replaced td_ithd with a thread private flag TDP_ITHREAD. - In statclock, check curthread against idlethread directly rather than curthread's proc against idlethread's proc. (Not really related to intr changes) Tested on: alpha, amd64, i386, sparc64 Tested on: arm, ia64 (older version of patch by cognet and marcel)

Eliminate two unused arguments to ttycreate().

2005-10-16T20:22:56Z

In uart_cnprobe(), fill in the cn_name field of the consdev structure.

2005-05-08T20:25:09Z

The core console code checks this field when a console is added and emits a warning if it's empty. In practice the warning is harmless for uart(4), because the cn_name is filled in as soon as the device name is known; which is when the device is enumerated. To avoid the warning, to avoid possible complications caused by emitting the warning without there (possibly) being a console selected yet and to avoid complications when the UART isn't found during bus enumeration, we just preset the cn_name field here to the name of the driver.

Start each of the license/copyright comments with /*-, minor shuffle of lines

2005-01-06T01:43:34Z

src-test2/sys/dev/uart/uart_tty.c, branch release/7.3.0_cvs