From: David Hinds <dhinds@sonic.net>
To: daniel.ritz@gmx.ch, Pavel Roskin <proski@gnu.org>,
Andrew Morton <akpm@osdl.org>,
linux-pcmcia <linux-pcmcia@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] yenta: irq-routing for TI bridges
Date: Tue, 24 Feb 2004 08:38:01 -0800 [thread overview]
Message-ID: <20040224163801.GA3398@sonic.net> (raw)
In-Reply-To: <20040224124011.A30975@flint.arm.linux.org.uk>
On Tue, Feb 24, 2004 at 12:40:11PM +0000, Russell King wrote:
>
> Not true. It has parallel ISA interrupts _and_ parallel PCI interrupts.
> It's a TI 1250. Unfortunately, the 1250 data sheet isn't available,
> however there seems to be some consistency in the device codes to
> features offered.
I have a TI 1250 data sheet (well 1250A, which is what I think you
actually have).
> The 1450 and 1251A (both of which seem similar to 1250) has separate pins
> for PCI parallel interrupts which are outside the control of the "IRQMUX"
> register. When these pins are not used for parallel PCI interrupts,
> they function as "GPIO3" and "IRQSER" (for PCI serial interrupts)
> respectively. The function of these pins is controlled by the device
> control register.
The 1250A is the same.
-- Dave
next prev parent reply other threads:[~2004-02-24 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 23:33 [PATCH] yenta: irq-routing for TI bridges Daniel Ritz
2004-02-24 0:00 ` Russell King
2004-02-24 0:32 ` Daniel Ritz
2004-02-24 1:06 ` Pavel Roskin
2004-02-24 11:59 ` Daniel Ritz
2004-02-24 12:40 ` Russell King
2004-02-24 15:23 ` Daniel Ritz
2004-02-24 23:26 ` [PATCH] yenta: irq-routing for TI bridges - take 2 Daniel Ritz
2004-02-25 6:55 ` Pavel Roskin
2004-02-25 20:03 ` Daniel Ritz
2004-02-25 21:20 ` Pavel Roskin
2004-02-25 23:01 ` Daniel Ritz
2004-02-24 16:38 ` David Hinds [this message]
2004-02-24 0:46 ` [PATCH] yenta: irq-routing for TI bridges Pavel Roskin
2004-02-24 12:44 ` Russell King
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=20040224163801.GA3398@sonic.net \
--to=dhinds@sonic.net \
--cc=akpm@osdl.org \
--cc=daniel.ritz@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.