X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C87A42.F56EBBCE@onstor-exch02.onstor.net>; Thu, 28 Feb 2008 12:48:58 -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: Thu, 28 Feb 2008 12:46:00 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E089F1674@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+wV95fFrXxdzRGKA3dXkPOwNlQCRscQw
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,

I'm looking at the interrupt issue right now.  Here's what I'm seeing
with the fancy command that you sent:

CB registers:
00: 00000000 00000006 30000859 00000000
10: 00000430 00000000 00000000 00000000
20: 00000000

ExCA registers:
00: 82 6f 90 70 00 08 41 02 - 00 00 0f 00 00 00 01 00
10: 00 08 00 88 00 68 80 00 - 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
40: 41 00 00 00 00

What are the CB registers?  From the ExCA registers, the setup looks
correct, and I'll now look at the PCI config registers more closely.

Also, are the functional interrupts working as expected?  I think these
were used to either signal that the card was ready or that a transfer
had completed.


Thanks,
Brian

=20

> -----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
