AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071003175742.7ccb9fda@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<jeff.miller@onstor.com>,<maxim.kozlovsky@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E05DD6F8F@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 3 Oct 2007 17:59:36 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>
Cc: "Jeff Miller" <jeff.miller@onstor.com>, Maxim Kozlovsky
 <maxim.kozlovsky@onstor.com>
Subject: Re: SSC I2C access
Message-ID: <20071003175936.4f8adc1f@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E05DD6F8F@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E018A6A0F@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E05DD6F8F@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Can we be more illucidating about what code we are talking about?  If
it's the code I think it is, it is userspace code, doesn't involve the
Linux kernel i2c driver subsystem at all then, and all the addresses
are the same (except being 64 bit) and it should very little
modification at all.  What am I missing?

Brian said as late as yesterday that all the addresses were the same,
so it should *almost* "just work."

Cheers,

a

PS The Linux kernel also has an SMBus driver for the SiByte so we won't
be using any of that cra^H^H^HPMON code regardless ~:^)

On Wed, 3 Oct 2007 17:29:54 -0700 "Brian Stark"
<brian.stark@onstor.com> wrote:

> 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
> 
> 
> > _____________________________________________ 
> > From: 	Jeff Miller  
> > Sent:	Wednesday, October 03, 2007 5:22 PM
> > To:	dl-Cougar
> > Subject:	SSC I2C access
> > 
> > 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.  
> > Thanks,
> > Jeff
