AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080225140848.3b74bfcd@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<warren.gale@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 25 Feb 2008 14:08:59 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Brian Stark <brian.stark@onstor.com>
Cc: Warren Gale <warren.gale@onstor.com>
Subject: concrete info on CF status problem
Message-ID: <20080225140859.55145d81@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,

I've finished researching the CF problem on recent build runs.  It
seems that neither the EXCA CSC register (offset 4) nor the CSC
interrupt are getting through.  One may be causing the other, but I
have no way of determining that.  The CSC register simply stays zero all
the time, which is why polling doesn't work either.

Is it possible some change to the PCI setup code in the PROM could be
causing this? I'm not even close to an expert on this part so I'm
just throwing out ideas....

FYI, you can look at the device registers from a running cougar.  At
the bash prompt, the command

# cat /sys/devices/pci0000\:00/0000\:00\:07.0/yenta_registers

will dump the registers for slot 0.  Change the 7.0 to 7.1 for the
second slot.

Cheers,

a
