X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8095E.DF9B726D@onstor-exch02.onstor.net>; Sun, 7 Oct 2007 19:54:06 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: kernel status of cougar CF
Date: Sun, 7 Oct 2007 19:54:10 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05DD7963@onstor-exch02.onstor.net>
In-Reply-To: <20071005160541.3f3d5c9e@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: kernel status of cougar CF
Thread-Index: AcgHpECjBrMD5GHOST6nwiPwQN1/XAAAQAWg
References: <20071005160541.3f3d5c9e@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Andy,

That is good news.  On the interrupts, the prom is already setting up
functional interrupts for both sockets.  This is done in both PCI config
registers as well as ExCA registers.  The prom is not setting up card
status change interrupts.

Not sure if interrupt 3 is correct.  Where are you getting this info?

Have you enabled PCI_INTA_L and PCI_INTB_L in the 1125 via the
interrupt_mask register?  I don't believe we have done this in PROM
since we don't use those interrupts.


Brian=20


> -----Original Message-----
> From: Andy Sharp=20
> Sent: Friday, October 05, 2007 4:06 PM
> To: Brian Stark
> Subject: kernel status of cougar CF
>=20
> Well, the good news is that I'm seeing the CF card and=20
> getting config info from it, the bad news is that the=20
> interrupt connection isn't happening.  The interrupt for the=20
> ide disk is getting set to 3, which I'm not really sure is=20
> right, but anyway, no interrupts are ever received on that=20
> line, so I get a continuous (slow) stream of
>=20
> hda: lost interrupt
>=20
> on the console.
>=20
> Any ideas?  Is that really the correct interrupt for the ide=20
> drive in the first slot?
>=20
> Cheers,
>=20
> a
>=20
