Re: [hppa-linux] Linker scripts and the boot loader

Re: [hppa-linux] Linker scripts and the boot loader

[Jason Eckhardt]

>
> Okay.  How does the boot loader work with loading the kernel?  I recall
> Jason saying something about the boot loader knowing how to load binaries.
>

  Currently, the bootloader assumes that the kernel is position independent
  and either straight binary or SOM (packed with ld -N). By "straight" binary
  I mean only the code and no headers, etc.
  I think HockeyPUX is linked at a certain address and is not position
  independent. I'm not sure why being inflexible like this is a win, but if
  necessary we could do the same.

  Also, since the loader assumes a binary image, the ELF image we produce
  will need to be massaged (same as x86 linux kernel, at least at one time).
  This was done because its simple to just read one record after the other
  into memory and execute.
  Alternatively, more code could be added to "understand" ELF. I prefer to
  keep the bootloader simple...it is just a bootloader after all.

  The simple dummy kernel you saw in the bootstrap tests is just a position
  independent binary loaded straight from the LIF and executed.

  Jason.

[hppa-linux] Linker scripts and the boot loader

[Alex deVries]

Okay.  How does the boot loader work with loading the kernel?  I recall
Jason saying something about the boot loader knowing how to load binaries.

What do we need from the kernel to get the boot loader to load some sort
of kernel?

Why do we need a custom linking in the first place?

- Alex

-- 
Alex deVries <puffin@redhat.com>     
Red Hat Contrib Net maintainer          
Ottawa, Canada  
PA RISC Linux Porting Team