AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080721103717.6951e5ef@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<jonathan.goldick@onstor.com>,<warren.gale@onstor.com>,<brian.stark@onstor.com>
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	BB375AF679D4A34E9CA8DFA650E2B04E0AFF17A9@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 21 Jul 2008 10:37:32 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Jonathan Goldick" <jonathan.goldick@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>, "Brian Stark"
 <brian.stark@onstor.com>
Subject: Re: need to get the cougar model information into the Linux kernel
 from Prom
Message-ID: <20080721103732.14a6a9d9@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0AFF17A9@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E0AFF17A9@onstor-exch02.onstor.net>
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 Mon, 21 Jul 2008 10:17:56 -0700 "Jonathan Goldick"
<jonathan.goldick@onstor.com> wrote:

> 	 <<Cougar configurations>> 
> 
> I have done the work on the EEE layer but need to get cpu count (based
> on model information in the SSC SEEP)  into the Linux kernel since I'm
> piggy-backing the information on the mgmt bus initialization
> (Mgmtbus_softc.ring_config ) rather than create an entirely new method
> of getting the SEEP information from the SSC to the EEE.  By putting
> this new information into the same region of memory as the mgmt bus
> information the code is pretty simple and can be tested quickly.
> 
> Now that you have context, I need to get the information from the SSC
> SEEP into the Mgmtbus_softc.ring_config data structure.  I have the
> option of trying to read the SEEP from kernel space or much better
> have the PROM hand it off the to kernel at init time as it does with
> other pieces of information.
> 
> Any suggestions on how we could get this done quickly and easily?

Not without changing the PROM and the kernel ~:^)

Changing just the kernel to read the seep should be trivial, unless
there is some uber-trick involved.  It is just reading memory
addresses, no?  Or perhaps some simple setup and then read memory
addresses?  I could stick it in the cougar platform code pretty easily,
or the management bus driver init routine as well.  Or, if the PROM
already sets one of the boot variables differently, the kernel could
just "guess" from that, since the numbers will be fixed?

Warren?

