X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C87A6D.2D5D853E@onstor-exch02.onstor.net>; Thu, 28 Feb 2008 17:51:11 -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 17:51:10 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E089F1902@onstor-exch02.onstor.net>
In-Reply-To: <20080228162754.3c0479e9@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: concrete info on CF status problem
Thread-Index: Ach6ae0SIzeKpjtxRjmiDh4RmWIQjAAABLYQ
References: <20080225140859.55145d81@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E089F185F@onstor-exch02.onstor.net> <20080228162754.3c0479e9@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>

No, I see nothing.  This is not a board problem -- the interrupt is
firing and something is then reading the status reg in the 1520. =20

I've tried your old Rev 2 board, a Rev 3 board, and a Rev 4 board.
Plus, I can show you the diffs in the netlists between Rev 2 - Rev 4,
and there's nothing in the hardware that's changed with any of the
connections between CF, 1520, and 1125.
=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Thursday, February 28, 2008 4:28 PM
> To: Brian Stark
> Cc: Warren Gale
> Subject: Re: concrete info on CF status problem
>=20
> On Thu, 28 Feb 2008 15:42:02 -0800 "Brian Stark"
> <brian.stark@onstor.com> wrote:
>=20
> > OK, I've verified the following:
> >=20
> > - Stop in PROM, eject a card, see both the PCI hardware=20
> interrupt with=20
> > the scope and the ExCA status-change interrupt reg (reg 4, bit 3),=20
> > status-change interrupt reg is clear on the next read
> > - Boot Linux, eject a card, see the PCI hardware interrupt with the=20
> > scope, do *not* see the ExCA status-change interrupt reg (reg 4, bit
> > 3) after doing a read with the 'cat /sys/devices' command.
> >=20
> > This is the case on both the old board and new board. =20
>=20
> Question: do you see 3-4 kernel messages come out on the=20
> console when you pull a card?  This is a characteristic of=20
> when things are working.
> I'm wondering if some boards are working and some not, out of=20
> the more recent ones, I mean.
>=20
