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

Andy,

Let's do a 1-1 tomorrow to catch up on stuff.  How about sometime before
the Cougar meeting?  Does 1:30pm work?

I'm heading back into the lab to work on your Cougar.  I'll let you know
when it's back up.


Brian
=20

> -----Original Message-----
> From: Andy Sharp=20
> 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=20
> doesn't have=20
> > anything you really want.  I also have to add a few wires=20
> to bring the=20
> > system up to the latest and greatest level, and then I want=20
> to run a=20
> > functional diags script to check the whole board out.
> >=20
> > I might have to swap your board with another so that this board can=20
> > have the PHY rework done on the TXRX.  I'll know more about this=20
> > later, but whatever the case, you'll have a system back today.
> >=20
> > By the way, did you find anything out with the 64-bit kernel on the=20
> > SWARM board?  We're still struggling with the cksseg stuff.
>=20
> Sigh, there never seems to be enough time to finish my status report.
>=20
> Anyway, on the SWARM board, I cannot get a 64 bit kernel to=20
> boot past the phase where the TLB handler functions are=20
> generated.  I spent yesterday and Friday porting our stuff to=20
> work on a recent commit to the kernel with changes to the=20
> cache handling code that some thought might fix our paging=20
> problem, but it didn't.
>=20
> I also spent a day or so last week trying to get our clock=20
> sources hooked up.  They don't work right on either bobcat or=20
> cougar.  I started with the bobcat because I thought I knew=20
> more about it, but I got nowhere: the RTC doesn't seem to=20
> increment or be settable, so obviously the driver is not=20
> functional.  Somehow the WD part of the driver manages to=20
> work, but not the rest.  The RTC driver class in the kernel=20
> has changed considerably since 2.6.12 or whenever the driver=20
> code I'm working with was originally written, so 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. =20
> And how you are intending to use them.  I understand that=20
> there is one built into the SoC and we add one of our own as=20
> well?  Is that correct?
>=20
> It looks like I'm going to have to figure out the paging=20
> problem myself, which means that's what I'll be doing most of=20
> this week and maybe next week.  Then I will have time to look=20
> at the module loading/cksseg problem.
>=20
> Cheers,
>=20
> a
>=20
