X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7FE60.3A4B3095@onstor-exch02.onstor.net>; Sun, 23 Sep 2007 20:06:05 -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: Sun, 23 Sep 2007 20:06:03 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05A25C6B@onstor-exch02.onstor.net>
In-Reply-To: <20070923111859.4207ba6f@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CF accesses in PROM
Thread-Index: Acf+DjeAwuZlKclVRuKVHxMHVIiJTQAUdHTQ
References: <BB375AF679D4A34E9CA8DFA650E2B04E05A25BE9@onstor-exch02.onstor.net> <20070923111859.4207ba6f@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

If you want to use a system tonight, you can use mine:

SSC 10.1.1.100 2001
Power 10.1.1.141 port .a3


=20

> -----Original Message-----
> From: Andy Sharp=20
> 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=20
> > PROM. This confirms that the hardware path to and from=20
> flash is ok and=20
> > also incorporates all the address changes we had to make to support=20
> > the CF from a SiByte.
> > =20
> > We tried getting the CF to be configured as memory instead=20
> of i/o, but=20
> > we hit some roadblocks with this.  For now, we are=20
> supporting the same=20
> > scheme that we've used before on Bobcat when accessing CF,=20
> which is a=20
> > mixture of i/o and memory accesses.  Here's the address map=20
> that we're=20
> > using on PCI in PROM:
> > =20
> > =20
> > Physical Address	 Size	 Function	 Notes=09
> > 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=09
> > 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=09
> > 1a00.0000	 16MB	 TXRX Shared Memory	 TXRX
> > accesses this locally at 0x9000.0000=09
> > 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=20
> > 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 today?
>=20
> Cheers,
>=20
> a
>=20
