X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8782C.627F8086@onstor-exch02.onstor.net>; Mon, 25 Feb 2008 21:02:20 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: concrete info on CF status problem
Date: Mon, 25 Feb 2008 21:01:44 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08822666@onstor-exch02.onstor.net>
In-Reply-To: <20080225140859.55145d81@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: concrete info on CF status problem
Thread-Index: Ach3+wV95fFrXxdzRGKA3dXkPOwNlQAL23sg
References: <20080225140859.55145d81@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>

Andy,

The PROM code doesn't set up CSC interrupts on the TI controller.  If
Linux is depending on that, then maybe that's why we're seeing this
issue.

I'll start with looking at the registers from a running Cougar and then
go from there.  I can't seem to get to my Cougar at the moment, so I'll
look at this tomorrow.


Brian


> -----Original Message-----
> From: Andy Sharp=20
> Sent: Monday, February 25, 2008 2:09 PM
> To: Brian Stark
> Cc: Warren Gale
> Subject: concrete info on CF status problem
>=20
> Hi Brian,
>=20
> I've finished researching the CF problem on recent build=20
> runs.  It seems that neither the EXCA CSC register (offset 4)=20
> nor the CSC interrupt are getting through.  One may be=20
> causing the other, but I have no way of determining that. =20
> The CSC register simply stays zero all the time, which is why=20
> polling doesn't work either.
>=20
> Is it possible some change to the PCI setup code in the PROM=20
> could be causing this? I'm not even close to an expert on=20
> this part so I'm just throwing out ideas....
>=20
> FYI, you can look at the device registers from a running=20
> cougar.  At the bash prompt, the command
>=20
> # cat /sys/devices/pci0000\:00/0000\:00\:07.0/yenta_registers
>=20
> will dump the registers for slot 0.  Change the 7.0 to 7.1=20
> for the second slot.
>=20
> Cheers,
>=20
> a
>=20
