AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20081103185933.7f585a79@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:exch1.onstor.net
NSV:
SSH:
R:<bfisher@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	490FB8A6.6020303@onstor.com
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 3 Nov 2008 18:59:45 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Bill Fisher <bfisher@onstor.com>
Subject: Re: Onstor prom support required for TuxRx SMP kernel
Message-ID: <20081103185945.056c80f0@ripper.onstor.net>
In-Reply-To: <490FB8A6.6020303@onstor.com>
References: <490FAAE3.3060802@onstor.com>
	<20081103184812.2db43358@ripper.onstor.net>
	<490FB8A6.6020303@onstor.com>
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, 3 Nov 2008 18:51:18 -0800 Bill Fisher <bfisher@onstor.com>
wrote:

> Andy Sharp wrote:
> > MT is the multithreaded mips processors designed by MIPS in recent
> > years.  So no, we don't have MT.  The start_secondary and so forth I
> > think I never actually sat down and wrote.  There must be some
> > routine in our prom that does this, and if not, then in our
> > runtime.  Shouldn't be too difficult to hack together anyway.
> > 
>    Maybe we should check the source into perforce. I can hack the
> changes using the cougar code to get around the externals and the
> calls to the various prom_XXX() procedures in
> arch/mips/kernel/setup.c code, etc.
> 
> I will proceed on that vector.
> 

OK.  Hopefully I will be out from under this RMC thing by tomorrow so I
can be more helpful.