AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070709101509.3de428c1@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 9 Jul 2007 10:16:07 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Brian Stark <brian.stark@onstor.com>
Subject: more irqy questions
Message-ID: <20070709101607.706add80@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Brian,

A controversy has sprung up which I'm hoping you can help with.  It
seems that there are two int's associated with the marvell and the
rm9k, namely 2 and 3.  I have code in the linux kernel to treat both 2
and 3 as cascaded interrupts.  But max says this doesn't make sense,
and that it should be only 3.  If that's true, then what should I be
doing with int 2?

According to the document, these correspond to

IRQ0 - MV64440 CPU_Int0
IRQ1 - MV64440 CPU_Int1

Despite having the marvell datasheet, I'm not quite sure what this
means.  IRQ0 in this case means interrupt 2 or whatever, obviously.  We
know that things basically work the way we expect if we setup int 3 as
the cascade interrupt, and setting up both int 2 and int 3 as
cascaded interrupts doesn't hurt anything, but of course we're only
part way into the process of getting everything ported over, so we
haven't tried everything yet.

Any thoughts?