AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080303103231.7a5d9828@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<warreng@localhost.localdomain>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	200802150207.m1F27rsv009910@localhost.localdomain
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 3 Mar 2008 10:32:55 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Warren Gale <warreng@localhost.localdomain>
Subject: Re: prom device driver for kernel
Message-ID: <20080303103255.71ce9100@ripper.onstor.net>
In-Reply-To: <200802150207.m1F27rsv009910@localhost.localdomain>
References: <200802150207.m1F27rsv009910@localhost.localdomain>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 14 Feb 2008 18:07:53 -0800 Warren Gale
<warreng@localhost.localdomain> wrote:

> what's the deal with prom device driver in ssc-mgmt-bus directory?
> bobcat only or??\

Hi Warren,

I got straightened out on this from Max.  This driver is for updating
the PROM on the SSC only.  The PROM upgrading of TXRX and FP is done by
sending messages to those nodes, where there is code in the runtime to
handle the upgrade.

Cheers,

a
