AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070423132308.7cf9ff35@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<warren.gale@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	BB375AF679D4A34E9CA8DFA650E2B04E035CB592@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 23 Apr 2007 13:23:22 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Warren Gale" <warren.gale@onstor.com>
Subject: Re: Cmd Line Args in PROM
Message-ID: <20070423132322.79be747a@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E035CB592@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E035CB592@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

Any words after the go command should be passed along.  There are
certain things that the PROM itself might try to parse out and do
something with.  I assume that's what the -e stuff is.

A word is any space delimited string.  It should parse them into
separate strings and create an array of pointers to those strings
exactly like the environment array.  Look for that code to be commented
out or if(ssc())'ed out or whatever.  But it should probably be after
it parses out things that it takes for itself, like -e or -s or -b and
any related options that go with those strings.

The order in memory is pointer to args, pointer to env, pointer to call
vectors.

Hope that helps,

Cheers,

a

On Mon, 23 Apr 2007 12:12:27 -0700 "Warren Gale"
<warren.gale@onstor.com> wrote:

> Andy,
> 
>    I have been digging in to the "go" command and her is what I see.
> 
>  
> 
>  
> 
>  
> 
> go ()
> 
> 
>   can take args, BUT
> 
>     if(isSSC()) you bypass all that
> 
>       do_bsd_launch( args  )
> 
>           load_launch_bsd((address_t)LOAD_BSD_ADDRESS);
> 
>            This gets some info from the system (Seep) bufs it up
> 
>            then jumps to the LOAD_BSD_ADDRESS with env_stings
> 
>             (*(PFI)addr)(1, av, env_strings);
> 
>  
> 
> So In Go there looks like there is code to parse the command line
> 
>   Looking for 's', 'b', or 'e'.
> 
>   Don't see a case where we are looking for "--" <args> to be passed
> on.
> 
>  
> 
>  
> 
>  
> 
> In the case of the SiByte processors we call:
> 
>     do_cmd("g -e 0xffffffff83000000");
> 
>     this calls go()  -- see above
> 
>  
> 
>  
> 
> I don't see where there might bee commented out code...
> 
> I'll need to understand the flow a bit better.
> 
> Maybe more info would help. Like what args ??
> 
>  
> 
> Thanks
> 
> Warren
> 
>  
> 
> PS sorry that It's taken so long.. I'm on it now :-)
> 
>  
> 
>  
> 
>  
> 
