X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C6FEF0.3F031529@onstor-exch02.onstor.net>; Thu, 2 Nov 2006 18:32:02 -0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C6FEF0.3F031529"
Content-class: urn:content-classes:message
Subject: RE: question about PROM size
Date: Thu, 2 Nov 2006 18:32:02 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E013846B5@onstor-exch02.onstor.net>
In-Reply-To: <20061102164647.3f8d07ef@ripper.onstor.net>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: question about PROM size
thread-index: Acb+4aMY/K0ooC7zQ1+Kv0RTFnD1pQAAYG7w
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Warren Gale" <warren.gale@onstor.com>
Cc: "Jay Michlin" <jay.michlin@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6FEF0.3F031529
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Andy,

Before answering your question about PROM size, let me talk a bit about
the Bobcat PROM architecture in general.  For each dual-processor in the
system (TXRX0/1, FP0/1, SSC/FC), there is a dedicated 'normal' and
'recovery' PROM.  The 'normal' PROM contains a couple of partitions --
boot, FPGA, and an unused diag partition -- while the 'recovery' PROM
contains just the boot partition.  The 'recovery' PROM is exactly what
the name implies -- if something goes wrong with the normal PROM on any
of the processors, the system can be booted from recovery.  This is done
via a jumper or through holding down the pushbutton reset for 15
seconds.  The latter method is used in the field (hopefully never
necessary!) since the jumper is only accessible by removing the top
cover.

We also use the recovery PROM for releasing new mfg diags to Ops.  The
diag application is part of the boot image and also can run from the
normal PROM.  However, in order to minimize upgrades, we do not
immediately push diag-related changes to the normal PROM.  Instead, we
push these to the recovery PROM, which we allow to be out of sync with
the normal, and then Ops upgrades systems in mfg with the new recovery
image.  When we do rev up the normal PROM, we then sync it with the
recovery image to pick up the diag changes, but we don't do a mandatory
field upgrade if the fixes are only to the diags.

With regards to the size, the normal PROM is 32Mbit (4Mx8) and the
recovery PROM is 4Mbit (512Kx8).  We have a large amount of space in all
partitions of the normal PROM, but we are getting very close with the
boot partition on the SiByte recovery PROM (see attached doc).  One of
Warren's upcoming projects is to start pulling stuff out of the PROM
that we no longer need.  If necessary, we may need to make the recovery
PROM a subset of functionality with respect to the normal, but we
hopefully won't get there. =20

As far as the software trees go, we have 2 trees called prom_bobcat and
diag_bc.  Typically, new development is done in diag_bc (since it's
mostly diag work at this point), and then eventually merged over to
prom_bobcat.  We have separate images for the SiBytes (TXRX0/1, FP0/1)
and RM9K (SSC/FC) that are built out of the same tree with a different
make target, which gives a total of 4 images (sibyte_bc.bin,
sibfimg_bc.bin, r9k.bin, r9kfimg.bin).  All 4 of these images can also
be built out of either tree, though, since there is currently no
distinction between normal and diag images.

Let me know if you have any questions on any of this. =20


Thanks,
Brian







=20

> -----Original Message-----
> From: Andrew Sharp [mailto:andy.sharp@onstor.com]=20
> Sent: Thursday, November 02, 2006 4:47 PM
> To: Brian Stark; Warren Gale
> Cc: Jay Michlin
> Subject: question about PROM size
>=20
> Hi Brian,
>=20
> Here's a question for you, which you might be able to answer=20
> by point me to various docs: how large is the prom on bobcat,=20
> and how much are we currently using?  I'm dreaming -- as=20
> usual -- about some new prom level things we might might want=20
> to do in cougar.  But first I should find out what the=20
> current prom can do and so forth.
>=20
> Thanks,
>=20
> a
>=20

------_=_NextPart_001_01C6FEF0.3F031529
Content-Type: text/plain;
	name="prom_partitions.txt"
Content-Transfer-Encoding: base64
Content-Description: prom_partitions.txt
Content-Disposition: attachment;
	filename="prom_partitions.txt"

Qm9iY2F0IFBST00gcGFydGl0aW9uczoNCg0KUk05MDAwIGltYWdlcyAtLQ0KDQpyOWsuYmluIChy
ZWNvdmVyeSkNCg0KICAgICAgICBwYXJ0X25hbWUgICAgICAgICAgIDogcjlrX3Jwcm9tDQogICAg
ICAgIHBhcnRfb2ZmcyAgICAgICAgICAgOiAweDANCiAgICAgICAgcGFydF9zaXplICAgICAgICAg
ICA6IDB4ODAwMDANCgl0b3RhbF9zaXplCSAgICA6IDB4NmUzOWQNCg0KDQpyOWtmaW1nLmJpbiAo
bm9ybWFsKQ0KDQogICAgICAgIHBhcnRfbmFtZSAgICAgICAgICAgOiByOWtfYm9vdA0KICAgICAg
ICBwYXJ0X29mZnMgICAgICAgICAgIDogMHgwDQogICAgICAgIHBhcnRfc2l6ZSAgICAgICAgICAg
OiAweGMwMDAwDQogICAgICAgIHRvdGFsX3NpemUJICAgIDogMHg2ZTM5ZA0KDQogICAgICAgIHBh
cnRfbmFtZSAgICAgICAgICAgOiByOWtfZGlhZyAodW51c2VkKQ0KICAgICAgICBwYXJ0X29mZnMg
ICAgICAgICAgIDogMHhjMDAwMA0KICAgICAgICBwYXJ0X3NpemUgICAgICAgICAgIDogMHhjMDAw
MA0KICAgICAgICB0b3RhbF9zaXplCSAgICA6IDB4NjhkZjQNCiANCiAgICAgICAgcGFydF9uYW1l
ICAgICAgICAgICA6IHN5cyAodW51c2VkKQ0KICAgICAgICBwYXJ0X29mZnMgICAgICAgICAgIDog
MHgxZjAwMDANCiAgICAgICAgcGFydF9zaXplICAgICAgICAgICA6IDB4MTAwMDANCiAgICAgICAg
dG90YWxfc2l6ZSAgICAgCSAgICA6IDB4MA0KDQoNCg0KU2lCeXRlIGltYWdlcyAtLQ0KDQpzaWJ5
dGVfYmMuYmluIChyZWNvdmVyeSkNCg0KICAgICAgICBwYXJ0X25hbWUgICAgICAgICAgIDogc2li
eXRlX3Jwcm9tDQogICAgICAgIHBhcnRfb2ZmcyAgICAgICAgICAgOiAweDANCiAgICAgICAgcGFy
dF9zaXplICAgICAgICAgICA6IDB4ODAwMDANCiAgICAgICAgdG90YWxfc2l6ZQkgICAgOiAweDc4
ZjIzDQogDQoNCg0Kc2liZmltZ19iYy5iaW4gKG5vcm1hbCkNCg0KICAgICAgICBwYXJ0X25hbWUg
ICAgICAgICAgIDogc2lieXRlX2Jvb3QNCiAgICAgICAgcGFydF9vZmZzICAgICAgICAgICA6IDB4
MA0KICAgICAgICBwYXJ0X3NpemUgICAgICAgICAgIDogMHhjMDAwMA0KICAgICAgICB0b3RhbF9z
aXplCSAgICA6IDB4Nzg1MzcNCiAgDQogICAgICAgIHBhcnRfbmFtZSAgICAgICAgICAgOiBzaWJ5
dGVfZGlhZyAodW51c2VkKQ0KICAgICAgICBwYXJ0X29mZnMgICAgICAgICAgIDogMHhjMDAwMA0K
ICAgICAgICBwYXJ0X3NpemUgICAgICAgICAgIDogMHhjMDAwMA0KICAgICAgICB0b3RhbF9zaXpl
CSAgICA6IDB4N2U3NWENCiANCg0KICAgICAgICBwYXJ0X25hbWUgICAgICAgICAgIDogbG11eF9o
ZXggKHVudXNlZCkNCiAgICAgICAgcGFydF9vZmZzICAgICAgICAgICA6IDB4MTgwMDAwDQogICAg
ICAgIHBhcnRfc2l6ZSAgICAgICAgICAgOiAweDgwMDAwDQogICAgICAgIHRvdGFsX3NpemUJICAg
IDogMHgyMzc2MA0KICANCiAgICAgICAgcGFydF9uYW1lICAgICAgICAgICA6IGx1Y19oZXgNCiAg
ICAgICAgcGFydF9vZmZzICAgICAgICAgICA6IDB4MjAwMDAwDQogICAgICAgIHBhcnRfc2l6ZSAg
ICAgICAgICAgOiAweDE4MDAwMA0KICAgICAgICB0b3RhbF9zaXplCSAgICA6IDB4NzU4MTkNCiAN
CglwYXJ0X25hbWUgICAgICAgICAgIDogc3lzICh1bnVzZWQpDQogICAgICAgIHBhcnRfb2ZmcyAg
ICAgICAgICAgOiAweDNmMDAwMA0KICAgICAgICBwYXJ0X3NpemUgICAgICAgICAgIDogMHgxMDAw
MA0KICAgICAgICB0b3RhbF9zaXplCSAgICA6IDB4MA0KIA==

------_=_NextPart_001_01C6FEF0.3F031529--
