X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8259D.C697D9BA@onstor-exch02.onstor.net>; Mon, 12 Nov 2007 18:34:55 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8259D.C697D9BA"
Content-class: urn:content-classes:message
Subject: RE: chassisd
Date: Mon, 12 Nov 2007 18:34:55 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E06883516@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0688330E@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: chassisd
Thread-Index: AcglS71ZJvzUhCe5TYGKlUUjIw8FsgALnfiQAAKh1kA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E06882F6D@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0688330E@onstor-exch02.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Tim Gardner" <tim.gardner@onstor.com>,
	"Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8259D.C697D9BA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Fan controller and temp sensor init are done in PROM version 1.0.2.
This is the version that I've put onto the 2 systems in the Elab that
Max and Andy will be using.  The 3rd system for Jeff will be installed
on Wednesday or Thursday once the chassis comes back from drop and
vibration test. =20


Brian


> _____________________________________________=20
> From: 	Tim Gardner =20
> Sent:	Monday, November 12, 2007 2:21 PM
> To:	Maxim Kozlovsky; dl-Cougar
> Subject:	RE: chassisd
>=20
> Chassisd is blocked pending prom code.=20
>=20
> Rendell, can you please hack chassisd for cougar so that it always
> reports the CPUs as up and running.
>=20
> Tim
>=20
>=20
> _____________________________________________
> From: Maxim Kozlovsky=20
> Sent: Monday, November 12, 2007 8:48 AM
> To: dl-Cougar
> Subject: chassisd
>=20
> What is the status of the chassis manager? If it is not close to
> working, can we quickly get something that hardwires the status of all
> cpus to up and running? There is a bunch of code that asks the chassis
> manager for the status of txrx and fp before proceeding, so working
> chassisd is required for further bringup.

------_=_NextPart_001_01C8259D.C697D9BA
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: chassisd</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Fan controller and =
temp sensor init are done in PROM version 1.0.2.&nbsp; This is the =
version that I've put onto the 2 systems in the Elab that Max and Andy =
will be using.&nbsp; The 3rd system for Jeff will be installed on =
Wednesday or Thursday once the chassis comes back from drop and =
vibration test.&nbsp; </FONT></P>
<BR>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Brian</FONT>
</P>
<BR>
<UL>
<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Tim Gardner&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Monday, November 12, 2007 2:21 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Maxim Kozlovsky; dl-Cougar</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: chassisd</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Chassisd is blocked =
pending prom code. </FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Rendell, can you =
please hack chassisd for cougar so that it always reports the CPUs as up =
and running.</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Tim</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Maxim Kozlovsky<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Monday, November 12, 2007 8:48 AM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> dl-Cougar<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> chassisd</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">What is the status of the chassis =
manager? If it is not close to working, can we quickly get something =
that hardwires the status of all cpus to up and running? There is a =
bunch of code that asks the chassis manager for the status of txrx and =
fp before proceeding, so working chassisd is required for further =
bringup.</FONT></P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C8259D.C697D9BA--
