From: Harvey Chapman <hchapman-linux-kernel@3gfp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial inter-character timeout usage with async io
Date: Tue, 07 Aug 2007 22:31:44 -0400 [thread overview]
Message-ID: <46B92B10.7@3gfp.com> (raw)
In-Reply-To: <46B92869.4000400@3gfp.com>
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.
next prev parent reply other threads:[~2007-08-08 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 22:53 [PATCH] serial inter-character timeout usage with async io Harvey Chapman
2007-08-08 1:11 ` Alan Cox
2007-08-08 2:20 ` Harvey Chapman
2007-08-08 2:31 ` Harvey Chapman [this message]
2007-08-08 8:47 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46B92B10.7@3gfp.com \
--to=hchapman-linux-kernel@3gfp.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).