X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C762A2.98AAF4A7@onstor-exch02.onstor.net>; Fri, 9 Mar 2007 16:28:08 -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: PROM load image comand
Date: Fri, 9 Mar 2007 16:28:08 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02C1B5B7@onstor-exch02.onstor.net>
In-Reply-To: <20070309151652.23b80e68@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PROM load image comand
Thread-Index: AcdioQWa3imL4kJuQ++GwcXCNTQr4QAADxug
References: <BB375AF679D4A34E9CA8DFA650E2B04E02C1B4BC@onstor-exch02.onstor.net><20070309141540.7b395cb2@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02C1B51F@onstor-exch02.onstor.net><20070309145306.2c57fe0e@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02C1B576@onstor-exch02.onstor.net> <20070309151652.23b80e68@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 think Warren understands what you're looking for with the PMON call
vectors since you guys have talked about it, but I don't know if he's
scoped the work yet.  It really depends on how soon you need something.


Brian



> -----Original Message-----
> From: Andy Sharp=20
> Sent: Friday, March 09, 2007 3:17 PM
> To: Brian Stark
> Cc: Warren Gale
> Subject: Re: PROM load image comand
>=20
> On Fri, 9 Mar 2007 15:09:49 -0800 "Brian Stark"
> <brian.stark@onstor.com> wrote:
>=20
> Ditto...
>=20
> > See below...
> >=20
> >=20
> > > -----Original Message-----
> > > From: Andy Sharp
> > > Sent: Friday, March 09, 2007 2:53 PM
> > > To: Brian Stark
> > > Cc: Warren Gale
> > > Subject: Re: PROM load image comand
> > >=20
> > > On Fri, 9 Mar 2007 14:40:23 -0800 "Brian Stark"
> > > <brian.stark@onstor.com> wrote:
> > >=20
> > > > Crap, those damn interrupts get me every time.  The 16552
> > > interrupts
> > > > are not hooked up to anything because all of the PMC
> > > interrupts were
> > > > already taken when the 16552 was added.  Same goes for the
> > > Marvell GPP
> > > > pins that could be wired up as interrupt inputs.
> > >=20
> > > So use the same int as the mpsc ports on the marvell. =20
> > > Interrupt sharing is not a problem.  As long as they're "like"=20
> > > interrupts.
> >=20
> >=20
> > This may be feasible since the interrupts are tri-stated=20
> when inactive=20
> > (high).  I could wire up the 16552 interrupt directly to=20
> the Marvell=20
> > interrupt output that's used for the BSD mpsc port, which=20
> looks to be=20
> > CPU_INT0_L from the Marvell.  Then when this interrupt fires to the=20
> > PMC, you'd have to go poll the Marvell cause register and then the
> > 16552 port to see who generated it.  Is this cool?  If so,=20
> I'll look=20
> > to see what the rework looks like.
> >=20
> > Of course, this is only needed if you can't get polling to work.
> > Software fixes for hardware mistakes are so much fun!
>=20
> I'll make you a deal: make me a PROM that gives me the=20
> standard PMON call vectors and I'll make the polling thing=20
> work.  Seriously.
>=20
> Cheers,
>=20
> a
>=20
