Re: [XenPPC] JS21/SLOF net boot commands

[Michal Ostrowski <mostrows@xxxxxxxxxxxxxx>]

If you're going to do all this below, why not just get yaboot to run?

The big issue that would prevent this from working is whether or not
SLOF implements the net device's "load" method (which it could implement
using the netboot word).

If you get yaboot to run then you can solve your dom0 and command-line
argument issues in one shot.

Also, is this configuration persistent?  (Or do you have to type this
stuff in on every boot? <barf>)   If not, then again, being able to run
yaboot, which would effectively execute a comparable sequence of code
would solve this problem.



-- 
Michal Ostrowski <mostrows@xxxxxxxxxxxxxx>




On Mon, 2006-06-19 at 16:35 -0400, Jimi Xenidis wrote:
> If you build Dom0 "into" your xen image do the following (simple  
> replace the patch with your tftpboot path):
> 
>    0> s" netboot 3000000 1000000 /tftpboot/slof/xen" snk
>    0> 3000000 load-elf-file start-elf
> 
> If you want to load Dom0 seperately then:
> 
>    0> s" netboot 4000000 1000000 /tftpboot/slof/dom0" snk
>    0> ciregs >r3 @
>    0> s" netboot 3000000 1000000 /tftpboot/slof/xen" snk
>    0> ciregs >r4 !
>    0> 4000000 ciregs >r3 !
>    0> 3000000 load-elf-file start-elf
> 
> 
> ***NOTE cutting and pasting a multi-line command can be dubious or  
> various serial protocols so this could be concatenated as one line an  
> pasted, all hail FORTH :)
> 
> 
> if you wanted to set a forth word that does thif it would look like:
>    : xen
>          s" netboot 4000000 1000000 /tftpboot/slof/dom0" snk
>          ciregs >r3 @
>          s" netboot 3000000 1000000 /tftpboot/slof/xen" snk
>          ciregs >r4 !
>          4000000 ciregs >r3 !
>          set-bootargs 3000000 load-elf-file start-elf
>    ;
> 
> This would perform all of the above but also allow for the  
> customization of boot parms and you would use as follows:
>    0> xen <bootargs>
> 
> 
> how exactly to make a forth word (at runtime or even in SLOF source)  
> is unknown to me personally but may fallow in this email thread?
> -JX
> 
> _______________________________________________
> Xen-ppc-devel mailing list
> Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ppc-devel
> 


_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel