Re: [PATCH] serial inter-character timeout usage with async io

Harvey Chapman wrote:
> just don't identify it specifically. In the ISRs, they simply check to
> see if any of bits 1, 2, or 3 are set. In the example above, on the last

Well, not entirely true, it actually checks bit 0 which indicates that
there was an interrupt, period. Bits 1, 2, and 3 indicate why the
interrupt occurred, but 8250.c and pxa.c ignore those bits.

-
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:
  • [PATCH] serial inter-character timeout usage with async io
    • From: Harvey Chapman <[email protected]>
  • Re: [PATCH] serial inter-character timeout usage with async io
    • From: Alan Cox <[email protected]>
  • Re: [PATCH] serial inter-character timeout usage with async io
    • From: Harvey Chapman <[email protected]>

• Prev by Date: Re: allow non root users to set io priority "idle" ?
• Next by Date: Re: why are some atomic_t's not volatile, while most are?
• Previous by thread: Re: [PATCH] serial inter-character timeout usage with async io
• Next by thread: Re: [PATCH] serial inter-character timeout usage with async io
• 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]