X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8061D.AF1C9C32@onstor-exch02.onstor.net>; Wed, 3 Oct 2007 16:29:54 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8061D.AF1C9C32"
Content-class: urn:content-classes:message
Subject: RE: SSC I2C access
Date: Wed, 3 Oct 2007 16:29:54 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05DD6F8F@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E018A6A0F@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SSC I2C access
Thread-Index: AcgGHJq2Jv4k/th5RJC3ft9kHjBUVQAAC6Dg
References: <BB375AF679D4A34E9CA8DFA650E2B04E018A6A0F@onstor-exch02.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Jeff Miller" <jeff.miller@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

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

Jeff,

As I mentioned yesterday in the meeting, we took the SiByte SMBus code
that is used in the FP/TXRX when getting this to work in the SSC PROM.
I think you should use that.


Brian


> _____________________________________________=20
> From: 	Jeff Miller =20
> Sent:	Wednesday, October 03, 2007 5:22 PM
> To:	dl-Cougar
> Subject:	SSC I2C access
>=20
> Currently the Cougar SSC code is using GT64440 addresses for I2C
> access.  This won't work, of course and I am working on cleaning that
> up now.  Does anyone know (or have an opinion about) if I should take
> the Sibyte SMbus code that is used in FP/TXRX and use that in the
> ssc-genlib/cm-util-bc.c Kseg1 access code (as in Bobcat and
> Bobcat-Linux) or if I should be trying to use the standard Linux I2C
> driver.  Using the I2C drive sounds cleaner and simpler but I have no
> idea if it works. =20
> Thanks,
> Jeff

------_=_NextPart_001_01C8061D.AF1C9C32
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: SSC I2C access</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Jeff,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">As I mentioned =
yesterday in the meeting, we took the SiByte SMBus code that is used in =
the FP/TXRX when getting this to work in the SSC PROM.&nbsp; I think you =
should use that.</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">Jeff Miller&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Wednesday, October 03, 2007 5:22 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">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">SSC I2C access</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Currently the Cougar SSC code is using =
GT64440 addresses for I2C access.&nbsp; This won&#8217;t work, of course =
and I am working on cleaning that up now.&nbsp; Does anyone know (or =
have an opinion about) if I should take the Sibyte SMbus code that is =
used in FP/TXRX and use that in the ssc-genlib/</FONT><FONT SIZE=3D2 =
FACE=3D"Tahoma">cm-util-bc.c Kseg1 access code (as in Bobcat and =
Bobcat-Linux) or if I should be trying to use the standard Linux I2C =
driver.&nbsp; Using the I2C drive sounds cleaner and simpler but I have =
no idea if it works.&nbsp; </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Thanks,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Tahoma">Jeff</FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C8061D.AF1C9C32--
