Re: Serial: UART_BUG_TXEN race conditions

linux-os (Dick Johnson) wrote:

With 8250 UARTs and clones, an interrupt occurs when the
transmitter holding register __becomes__ empty. That means
it must have had something in it.

Dear Wrongbot,

That's what some people think, and that's how they end up shipping buggy hardware.

With 16x50 UARTs, an interrupt occurs *when an interrupt condition is asserted*, which can happen either though a state change or on a change in IER.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Serial: UART_BUG_TXEN race conditions
    • From: Ingo van Lil <[email protected]>
  • Re: Serial: UART_BUG_TXEN race conditions
    • From: "linux-os \(Dick Johnson\)" <[email protected]>

• Prev by Date: Re: Kernel API Reference Documentation
• Next by Date: [PATCH] remove include of screen_info.h from tty.h
• Previous by thread: Re: Serial: UART_BUG_TXEN race conditions
• Next by thread: Fw: [PATCH 0/2] srcu: add RCU variant that permits read-side blocking
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]