X-Sylpheed-Account-Id:1
S:andy.sharp@onstor.com
SCF:#mh/Mailbox/sent
X-Sylpheed-Sign:0
X-Sylpheed-Encrypt:0
X-Sylpheed-Privacy-System:
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E089F169F@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 28 Feb 2008 15:42:24 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>
Subject: Re: concrete info on CF status problem
Message-ID: <20080228154224.5a7db658@ripper.onstor.net>
References: <20080225140859.55145d81@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E089F169F@onstor-exch02.onstor.net>
Organization: Onstor
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 28 Feb 2008 12:05:24 -0800 "Brian Stark"
<brian.stark@onstor.com> wrote:

> Here's what I see after ejecting a card:
>           
> CB registers:
> 00: 00000000 00000006 30000286 00000000
> 10: 00000400 00000000 00000000 00000000
> 20: 00000000
> 
> ExCA registers:
> 00: 82 00 00 50 00 08 00 00 - 00 00 01 00 00 00 01 00
                  ^^ <-those are the bits that should change
> 10: 00 00 00 00 00 00 c0 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: 00 00 00 00 00 
> 
> The 0x01 ExCA register is showing that the card is no longer there.
> Not sure why the interrupt status in 0x04 isn't showing that the card
> was ejected.
> 
> I'll keep looking, but worse comes to worse, I suppose you could poll
> the 0x01 register to see if a card is installed or removed.

Nope.  Tried that.  Driver doesn't seem to care.  Although I didn't try
that hack in conjunction with irqpoll.  But I'm loathe to do multiple
hacks like this when it seems they shouldn't be necessary.  All this
stuff was working as expected on previous revs of </everything>.

> 
> 
> Brian
> 
> 
> > -----Original Message-----
> > From: Andy Sharp 
> > Sent: Monday, February 25, 2008 2:09 PM
> > To: Brian Stark
> > Cc: Warren Gale
> > Subject: concrete info on CF status problem
> > 
> > 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
> > 
