Re: [Etherboot-developers] Porting question

[<ke...@us...>]

>>Etherboot needs to be stripped down?
>>
>It was a wrong phrase of mine. I mean that I am trying to comment-out 
>everything related to x86.

Still the wrong idea. You shouldn't need to do that. Eric has done a
brilliant job separating out the non-architecture specific components
from the architecture specific ones. Ideally you should only need to
create a new branch in arch and new config files at the top level.  If
not tell us what needs to be fixed.

>>I would recommend writing a mkelf for your platform that packages
>>kernels ramdisks and everything together, instead of adding a COFF
>>handler.  But it is your port...
>>
>This is not very clear to me. Initially I will try to add the COFF 
>loader and if it is not possible I will come-back again.

Whatever loader format you choose, it has to have some kind of directory
at the beginning to indicate where the pieces go in memory. Etherboot
supports NBI and ELF. Instead of writing COFF support, try to see if you
can write an ELF generator, then you don't need to implement it in
Etherboot since it already has an ELF loader. You may need to write a
custom one anyway because of the need to load ramdisks.