X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C80F8C.5F69F72B@onstor-exch02.onstor.net>; Mon, 15 Oct 2007 16:34:55 -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: Cougar board
Date: Mon, 15 Oct 2007 16:34:55 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E060D0D64@onstor-exch02.onstor.net>
In-Reply-To: <20071015165921.311b0ce4@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar board
Thread-Index: AcgPh2ijKfoBSaqzRfaSApBdOAECZQABNARA
References: <BB375AF679D4A34E9CA8DFA650E2B04E05FEACA7@onstor-exch02.onstor.net><20071015104004.4bdabb81@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E05FEAD4C@onstor-exch02.onstor.net><20071015105504.35ec8040@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E05FEAEC8@onstor-exch02.onstor.net> <20071015165921.311b0ce4@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Andy,

Your Cougar is ready to go.  It was done around 3:30, but of course, I
forgot to let you know that!


Brian
=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Monday, October 15, 2007 4:59 PM
> To: Brian Stark
> Subject: Re: Cougar board
>=20
> How's my coug doing?
>=20
> On Mon, 15 Oct 2007 13:30:20 -0700 "Brian Stark"
> <brian.stark@onstor.com> wrote:
>=20
> > Andy,
> >=20
> > Let's do a 1-1 tomorrow to catch up on stuff.  How about sometime=20
> > before the Cougar meeting?  Does 1:30pm work?
> >=20
> > I'm heading back into the lab to work on your Cougar.  I'll let you=20
> > know when it's back up.
> >=20
> >=20
> > Brian
> > =20
> >=20
> > > -----Original Message-----
> > > From: Andy Sharp
> > > Sent: Monday, October 15, 2007 10:55 AM
> > > To: Brian Stark
> > > Subject: Re: Cougar board
> > >=20
> > > On Mon, 15 Oct 2007 10:43:45 -0700 "Brian Stark"
> > > <brian.stark@onstor.com> wrote:
> > >=20
> > > > Yes, we'll be doing a prom upgrade, although it probably
> > > doesn't have
> > > > anything you really want.  I also have to add a few wires
> > > to bring the
> > > > system up to the latest and greatest level, and then I want
> > > to run a
> > > > functional diags script to check the whole board out.
> > > >=20
> > > > I might have to swap your board with another so that this board=20
> > > > can have the PHY rework done on the TXRX.  I'll know more about=20
> > > > this later, but whatever the case, you'll have a system back=20
> > > > today.
> > > >=20
> > > > By the way, did you find anything out with the 64-bit kernel on=20
> > > > the SWARM board?  We're still struggling with the cksseg stuff.
> > >=20
> > > Sigh, there never seems to be enough time to finish my status=20
> > > report.
> > >=20
> > > Anyway, on the SWARM board, I cannot get a 64 bit kernel to boot=20
> > > past the phase where the TLB handler functions are generated.  I=20
> > > spent yesterday and Friday porting our stuff to work on a recent=20
> > > commit to the kernel with changes to the cache handling code that=20
> > > some thought might fix our paging problem, but it didn't.
> > >=20
> > > I also spent a day or so last week trying to get our=20
> clock sources=20
> > > hooked up.  They don't work right on either bobcat or cougar.  I=20
> > > started with the bobcat because I thought I knew more=20
> about it, but=20
> > > I got nowhere: the RTC doesn't seem to increment or be=20
> settable, so=20
> > > obviously the driver is not functional.  Somehow the WD=20
> part of the=20
> > > driver manages to work, but not the rest.  The RTC driver=20
> class in=20
> > > the kernel has changed considerably since 2.6.12 or whenever the=20
> > > driver code I'm working with was originally written, so=20
> there is a=20
> > > bit of work there for me to do.
> > >=20
> > > I would appreciate some of your time to educate me on the RTC=20
> > > situation on cougar.  Interrupts, addresses and so forth.
> > > And how you are intending to use them.  I understand that=20
> there is=20
> > > one built into the SoC and we add one of our own as well?=20
>  Is that=20
> > > correct?
> > >=20
> > > It looks like I'm going to have to figure out the paging problem=20
> > > myself, which means that's what I'll be doing most of=20
> this week and=20
> > > maybe next week.  Then I will have time to look at the module=20
> > > loading/cksseg problem.
> > >=20
> > > Cheers,
> > >=20
> > > a
> > >=20
>=20
