From: Paul Fulghum <paulkf@microgate.com>
To: Shaun Jackman <sjackman@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: TL16C752B DUART: MCR_OUT2 disables interrupts
Date: Tue, 20 Jun 2006 15:37:29 -0500 [thread overview]
Message-ID: <44985C89.3040000@microgate.com> (raw)
In-Reply-To: <7f45d9390606201335x29957bfcy31dd4ece97d551ea@mail.gmail.com>
Shaun Jackman wrote:
> On 6/20/06, Paul Fulghum <paulkf@microgate.com>
> I didn't know of this historic use of the OUT2 pin to disable
> interrupts. I'll put OUT2 on my list of things not to muck with. Is
> there any similar historic use of OUT1?
Not that I'm aware of. All of the old designs I've
seen left that signal unconnected.
--
Paul Fulghum
Microgate Systems, Ltd.
prev parent reply other threads:[~2006-06-20 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 20:07 TL16C752B DUART: MCR_OUT2 disables interrupts Shaun Jackman
2006-06-20 20:26 ` Paul Fulghum
2006-06-20 20:35 ` Shaun Jackman
2006-06-20 20:37 ` Paul Fulghum [this message]
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=44985C89.3040000@microgate.com \
--to=paulkf@microgate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sjackman@gmail.com \
/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