From: Sergei Shtylyov <sshtylyov@ru•mvista.com>
To: "Leisner, Martin" <Martin.Leisner@xerox•com>
Cc: "Lund, Nathan" <Nathan.Lund@xerox•com>, linuxppc-embedded@ozlabs•org
Subject: Re: how are the interrupts mapped on the taiga board?
Date: Fri, 08 Jun 2007 00:17:39 +0400 [thread overview]
Message-ID: <466867E3.9030505@ru.mvista.com> (raw)
In-Reply-To: <556445368AFA1C438794ABDA8901891C066B5AC5@usa0300ms03.na.xerox.net>
Leisner, Martin wrote:
> I'm looking at mpc7448hpc2.dts -- and the tsi108 specs...
> I see how TTYS0 is IRQ12 and the ethernet is IRQ16...that agrees with
> the file...
> and the tundra TSi108 spec.
> But in after we boot in /proc/interrupts:
>
> 16: 1796 Tsi108_PIC Edge serial
> 18: 24148 Tsi108_PIC Level eth0
> I don't see in the .dts a mapping from 12->16 and 16->18.
> Nore have I found anything in the source...
> I using 2.6.21.1.
> How is this done?
It's done by arch/powerpc kernel itself which remaps any IRQs < 16.
WBR, Sergei
prev parent reply other threads:[~2007-06-07 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 19:55 how are the interrupts mapped on the taiga board? Leisner, Martin
2007-06-07 20:17 ` Sergei Shtylyov [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=466867E3.9030505@ru.mvista.com \
--to=sshtylyov@ru$(echo .)mvista.com \
--cc=Martin.Leisner@xerox$(echo .)com \
--cc=Nathan.Lund@xerox$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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