X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B86B.3E5D2CDC@onstor-exch02.onstor.net>; Tue, 26 Jun 2007 19:28:35 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: compac flash LEDs
Date: Tue, 26 Jun 2007 19:28:35 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0451D6F2@onstor-exch02.onstor.net>
In-Reply-To: <20070626164941.0455efcc@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: compac flash LEDs
Thread-Index: Ace4TKpuNxRtWbRJQsGCAYKJazVE5AAHDmiw
References: <20070626144241.58dc4fcc@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E0451D575@onstor-exch02.onstor.net> <20070626164941.0455efcc@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Warren Gale" <warren.gale@onstor.com>

My comments below...

=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Tuesday, June 26, 2007 4:50 PM
> To: Warren Gale
> Cc: Brian Stark
> Subject: Re: compac flash LEDs
>=20
> On Tue, 26 Jun 2007 15:35:09 -0700 "Warren Gale"
> <warren.gale@onstor.com> wrote:
>=20
> > Andy,
> >    See inline  < >
> > Warren
> >=20
> > -----Original Message-----
> > From: Andy Sharp
> > Sent: Tuesday, June 26, 2007 2:43 PM
> > To: Warren Gale
> > Cc: Brian Stark
> > Subject: compac flash LEDs
> >=20
> > As opposed to compact flash LEDs.
> >=20
> > Q1:
> >=20
> > Anyway, just curious who/what handles the LEDs by the compact flash.
> > Does the PROM do that?=20
> >=20
> > <PROM does NOT do anything with these LED's>
> >=20
> >  Could the OS do that?=20
> >=20
> > <U bet, all yours>
>=20
> that's funny
> now tell me how to program them, you bastaaaaaaaaaaaaards!

Ah, LEDs are my favorite topic.  Chassisd controls the CF LEDs, and the
definition is as follows:

CF - green =3D ok to eject (secondary CF); amber =3D do not eject =
(primary
CF)

There was much angst over this color scheme, and I don't think it's
gonna change.

The LEDs are programmed by setting the following bits in the Marvell
GPIO register:

Bit Dir Description
31:30 O CF1 LED (00 =3D off; 01 =3D red; 10 =3D green; 11 =3D amber)
29:28 O CF0 LED (00 =3D off; 01 =3D red; 10 =3D green; 11 =3D amber)

The GPIO base register is at virtual 0xbc00f104.




>=20
> >  I was thinking that the
> > LED should be red if a filesystem on the CF card was=20
> mounted R/W, so=20
> > that the user would know not to pull a CF card if it was mounted.
> >=20
> > <Might have a problem with the color "RED". If I'm not mistaken, in=20
> > European markets the color "RED" means "Emergency" "Power=20
> Down" Maybe=20
> > this has changed, but I remember changing lots of LED's...>
>=20
> Green and whatever.  Geez, get on with it.
>=20
> >=20
> > Q2:
> >=20
> > Is the pd6729 interrupt(s) edge or level?  Are they any=20
> different from=20
> > the natsemi interrupts?  We don't use them for OpenBSD, so I'm=20
> > breaking new ground here.
> >=20
> > < U mean the Intel pd6729 and the TI1520?
> >   PROM does very little with this and I don't know off hand. Sorry>
>=20
> No, I mean the Cirrus/Intel pd6729 and the Natsemi dp83816=20
> ethernet controllers, that also have interrupts on them.
>

With the exception of the NMI, all interrupts to the RM9K are level
sensitive.

Also, I am almost positive that the Natsemi interrupts are used in
OpenBSD.  I specifically added these to the RM9K to INT6_L and INT7_L on
the Rev 2 Bobcats.  The Rev 1 Bobcats were retired because they didn't
have this interrupt support.






=20
> >=20
> >=20
> >=20
> > Cheers,
> >=20
> > a
>=20
