Subject: Question about MILO
From: Hyung Min SEO (HMSEO@sec.samsung.com)
Date: Wed Apr 07 1999 - 02:18:09 PDT 

Hi all 

I studied the milo object. 
The milo is composed of sevaral parts( micropal, relocate, osfpal, stub, 
milo ). 
The linload store the milo to memory ( 0x8 0000 in my LX box ) and the PC 
jumps to micropal. 
The micropal move the other parts( relocate, osfpal, stub, milo ) to 0x30 
0000 and the PC jumps to relocate. 
The relocate move the other parts( osfpal, stub, milo ) to 0x20 0000 and 
the PC jumps to osfpal. 
The osfpal execute and the PC jumps to stub. 
The stub move the milo to 0xd0 0000 and the milo start to work. 
Is it right? 

I don't know why the relocate move the other parts to 0x20 0000. 
If the block of composed osfpal, stub, milo remains at same place(0x30 
0b00) then there is any problem? 

Regards. 


Subject: Re: Question about MILO
From: Nikita Schmidt (cetus@snowball.ucd.ie)
Date: Wed Apr 07 1999 - 08:05:43 PDT 

On Wednesday, 7 Apr, Hyung Min SEO wrote: 
> 
> I don't know why the relocate move the other parts to 0x20 0000. 
> If the block of composed osfpal, stub, milo remains at same place(0x30 
> 0b00) then there is any problem? 
> 

I believe this is due to historical reasons. As I understand it, there 
is no actual need for the second relocation, if micropal moves the whole 
thing to 0x1ff500 from the very beginning. (MILO can't stay at 0x300b00 
because it will be overwritten by the kernel.) 

I am currenly planning a big MILO cleanup, and have already rewritten 
micropal to eliminate the need in relocate. 

Nikita
