AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071007234440.0d2d2480@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E05DD7963@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Sun, 7 Oct 2007 23:44:57 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>
Subject: Re: kernel status of cougar CF
Message-ID: <20071007234457.5fad1c54@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E05DD7963@onstor-exch02.onstor.net>
References: <20071005160541.3f3d5c9e@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E05DD7963@onstor-exch02.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

On Sun, 7 Oct 2007 20:54:10 -0700 "Brian Stark"
<brian.stark@onstor.com> wrote:

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

Yeah, it seems like we are pretty close, just need to nail down the
interrupt situation.

I'd really like to do the status change interrupts this time, LGI.
And besides god, the driver likes it so much better too.  As I
mentioned, it doesn't need to be a PROM thing, if I can do it myself
somewhere.

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

I really don't know.  It doesn't start out with any value at all and
doesn't seem to get anything from any PCI config action. Then it
suddenly comes up with it from somewhere.  The whole reason I mention
it is it doesn't sound right.  Probably some generic kernel IRQ probing
stuff.
 
> 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.

Please.  I don't get my hands dirty doing stuff like that.  The generic
sibyte code does whatever it does.  But really, I'm not sure what
you're getting at.

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