Searched hist:"44 ed791b" (Results 1 – 3 of 3) sorted by relevance
/freebsd/sys/dev/uart/ |
H A D | uart_dev_z8530.c | 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip.
|
H A D | uart_core.c | 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip.
|
H A D | uart_dev_ns8250.c | 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip. 44ed791b Wed Sep 17 03:11:32 GMT 2003 Marcel Moolenaar <marcel@FreeBSD.org> In uart_intr() loop until all interrupts have been handled. Previously an UART interface could get stuck when a new interrupt condition arose while servicing a previous interrupt. Since an interrupt was already pending, no new interrupt would be triggered.
Avoid infinite recursion by flushing the Rx FIFO and marking an overrun condition when we could not move the data from the Rx FIFO to the receive buffer in toto. Failure to flush the Rx FIFO would leave the Rx ready condition pending.
Note that the SAB 82532 already did this due to the nature of the chip.
|