X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7FF9E.C6BF56BC@onstor-exch02.onstor.net>; Tue, 25 Sep 2007 10:06: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: CF accesses in PROM
Date: Tue, 25 Sep 2007 10:06:22 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05B4680F@onstor-exch02.onstor.net>
In-Reply-To: <20070925104905.616d2597@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CF accesses in PROM
Thread-Index: Acf/nF3qWRIvm2RoQmicWmclP/dlFgAAJICw
References: <BB375AF679D4A34E9CA8DFA650E2B04E05A25BE9@onstor-exch02.onstor.net><20070923111859.4207ba6f@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E05A25C6B@onstor-exch02.onstor.net><20070923231155.5ac105d0@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E05B4618E@onstor-exch02.onstor.net> <20070925104905.616d2597@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Try another Cougar that has an older PROM with no CF support yet.  You
still need to hit 'b' with this board:

SSC 10.1.1.100 2015
Power 10.1.1.102 port .a3

We were having some networking issues earlier today, so maybe that's
what you were seeing.  Let me know how it looks.


Brian


> -----Original Message-----
> From: Andy Sharp=20
> Sent: Tuesday, September 25, 2007 10:49 AM
> To: Brian Stark
> Subject: Re: CF accesses in PROM
>=20
> Hmm. I may not have to hit 'b' anymore, but I can't load a=20
> kernel either.  The load command just keeps spinning its=20
> spinner and never completes.  Also, I don't notice any=20
> appreciable network I/O to the tftp server either.  It might=20
> just be a few bytes per second, but not the previous 100KB/s or so.
>=20
>=20
> On Mon, 24 Sep 2007 11:08:32 -0700 "Brian Stark"
> <brian.stark@onstor.com> wrote:
>=20
> > Andy,
> >=20
> > Your system is back up and is powered on.  I had a temporary mental=20
> > lapse last night and upgraded the Cougar board with a Bobcat PROM=20
> > image. Oops.
> >=20
> > By the way, you don't have to hit 'b' anymore to boot the=20
> system.  It=20
> > automatically comes up to a prompt.
> >=20
> >=20
> > Brian
> >=20
> >=20
> > > -----Original Message-----
> > > From: Andy Sharp
> > > Sent: Sunday, September 23, 2007 11:12 PM
> > > To: Brian Stark
> > > Subject: Re: CF accesses in PROM
> > >=20
> > > That's OK, I'll wait until tomorrow.
> > >=20
> > > On Sun, 23 Sep 2007 21:06:03 -0700 "Brian Stark"
> > > <brian.stark@onstor.com> wrote:
> > >=20
> > > > If you want to use a system tonight, you can use mine:
> > > >=20
> > > > SSC 10.1.1.100 2001
> > > > Power 10.1.1.141 port .a3
> > > >=20
> > > >=20
> > > > =20
> > > >=20
> > > > > -----Original Message-----
> > > > > From: Andy Sharp
> > > > > Sent: Sunday, September 23, 2007 11:19 AM
> > > > > To: Brian Stark
> > > > > Cc: dl-Cougar
> > > > > Subject: Re: CF accesses in PROM
> > > > >=20
> > > > > On Sun, 23 Sep 2007 11:15:55 -0700 "Brian Stark"
> > > > > <brian.stark@onstor.com> wrote:
> > > > >=20
> > > > > > Just wanted to let you know that we now have CF
> > > accesses working
> > > > > > in PROM. This confirms that the hardware path to and from
> > > > > flash is ok and
> > > > > > also incorporates all the address changes we had to make to=20
> > > > > > support the CF from a SiByte.
> > > > > > =20
> > > > > > We tried getting the CF to be configured as memory instead
> > > > > of i/o, but
> > > > > > we hit some roadblocks with this.  For now, we are
> > > > > supporting the same
> > > > > > scheme that we've used before on Bobcat when accessing CF,
> > > > > which is a
> > > > > > mixture of i/o and memory accesses.  Here's the address map
> > > > > that we're
> > > > > > using on PCI in PROM:
> > > > > > =20
> > > > > > =20
> > > > > > Physical Address	 Size	 Function
> > > > > > Notes 0000.0400	 256	 CF Controller I/O socket A
> > > > > > Accessed at base of 0xdc000000; set in ExCA i/o 0=09
> > > > > > 0000.0800	 256	 CF Controller I/O socket B
> > > > > > Accessed at base of 0xdc000000; set in ExCA i/o 0=09
> > > > > > 0001.0000	 64KB	 CF Controller I/O ExCA
> > > > > > Accessed at base of 0xdc000000; uses base/index scheme=09
> > > > > > 0080.0000	 64KB	 CF Controller Memory
> > > > > > Socket memory accesses (set in ExCA memory 0); accessed at
> > > > > > base of 0xf8.0000.0000 0081.0000	 64KB	 CF
> > > > > > Controller Socket A / ExCA base	 Socket A memory
> > > > > > accesses; ExCA mapped at 0x800 offset; accessed at base of
> > > > > > 0xf8.0000.0000 0082.0000	 64KB	 CF Controller
> > > > > > Socket B / ExCA base	 Socket B memory accesses; ExCA
> > > > > > mapped at 0x800 offset; accessed at base of
> > > > > > 0xf8.0000.0000 1a00.0000	 16MB	 TXRX Shared
> > > > > > Memory	 TXRX accesses this locally at
> > > > > > 0x9000.0000 1b00.0000	 16MB	 FP Shared
> > > > > > Memory	 FP accesses this locally at 0x9000.0000=09
> > > > > > 1f40.0000	 64KB	 BM FPGA	  =09
> > > > > > 6000.0000	 16MB	 SSC Shared Memory	 SSC
> > > > > > accesses this locally at 0x8300.0000=09
> > > > > > =20
> > > > > > =20
> > > > > > Andy, let Linux take over and do whatever it likes.  We
> > > know that
> > > > > > accesses to all the above paths work.
> > > > > > =20
> > > > > > =20
> > > > > > Brian
> > > > > > =20
> > > > >=20
> > > > > OK.  I assume you are going to add these changes to my PROM=20
> > > > > today?
> > > > >=20
> > > > > Cheers,
> > > > >=20
> > > > > a
> > > > >=20
> > >=20
>=20
