X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C80FA3.4512B54A@onstor-exch02.onstor.net>; Mon, 15 Oct 2007 19:18:49 -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 19:18:48 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E060D0DE4@onstor-exch02.onstor.net>
In-Reply-To: <20071015182028.1eb069d0@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar board
Thread-Index: AcgPkr2pAH4r5fAFSFCE4Ay7TYwB7wAEFDGw
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><BB375AF679D4A34E9CA8DFA650E2B04E060D0D7A@onstor-exch02.onstor.net> <20071015182028.1eb069d0@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

I added the top slot CF via the CF riser board, but I didn't touch the
bottom slot.  I can remove the CF riser if you like.


Brian


> -----Original Message-----
> From: Andy Sharp=20
> Sent: Monday, October 15, 2007 6:20 PM
> To: Brian Stark
> Subject: Re: Cougar board
>=20
> Hey!  What did you boneheads do with my CF card!?  CF card=20
> violators shall be keeld!
>=20
> On Mon, 15 Oct 2007 17:44:08 -0700 "Brian Stark"
> <brian.stark@onstor.com> wrote:
>=20
> > Can you meet at 1pm tomorrow instead of 1:30?  I have=20
> another meeting=20
> > at 1:30 that was just scheduled.
> >=20
> >=20
> > Brian
> >=20
> > =20
> >=20
> > > -----Original Message-----
> > > From: Andy Sharp
> > > 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=20
> 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=20
> > > > you 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=20
> > > > > > board can have the PHY rework done on the TXRX.  I'll know=20
> > > > > > more about this later, but whatever the case, you'll have a=20
> > > > > > system back today.
> > > > > >=20
> > > > > > By the way, did you find anything out with the=20
> 64-bit kernel=20
> > > > > > on the SWARM board?  We're still struggling with the cksseg=20
> > > > > > 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=20
> kernel to boot=20
> > > > > past the phase where the TLB handler functions are=20
> generated.  I=20
> > > > > spent yesterday and Friday porting our stuff to work=20
> on a recent=20
> > > > > commit to the kernel with changes to the cache handling code=20
> > > > > that 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
> > > clock sources
> > > > > hooked up.  They don't work right on either bobcat or cougar.
> > > > > I started with the bobcat because I thought I knew more
> > > about it, but
> > > > > I got nowhere: the RTC doesn't seem to increment or be
> > > settable, so
> > > > > obviously the driver is not functional.  Somehow the WD
> > > part of the
> > > > > driver manages to work, but not the rest.  The RTC driver
> > > class in
> > > > > the kernel has changed considerably since 2.6.12 or=20
> whenever the=20
> > > > > driver code I'm working with was originally written, so
> > > there is a
> > > > > 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
> > > there is
> > > > > one built into the SoC and we add one of our own as well?=20
> > >  Is that
> > > > > correct?
> > > > >=20
> > > > > It looks like I'm going to have to figure out the=20
> paging problem=20
> > > > > myself, which means that's what I'll be doing most of
> > > this week and
> > > > > maybe next week.  Then I will have time to look at the module=20
> > > > > loading/cksseg problem.
> > > > >=20
> > > > > Cheers,
> > > > >=20
> > > > > a
> > > > >=20
> > >=20
>=20
