A quick update
After an enormous amount of frustration (with fault only to me, I should have thought that there was a second bootpserver on my network), the kernel tree in CVS actually builds on HPUX. This is really just Jason's work glued into the kernel tree.
Next:
- we need an HPUX ld linker script to resolve the vmlinux building, what's the format for this?
- we need to figure out why the bootloader gives an error when loading the kernel into memory
- Alex
Signature · 3 lines
Alex deVries Vice President of Engineering The Puffin Group
In message <[email protected]>you write:
Quoted 2 lines
- we need an HPUX ld linker script to resolve the vmlinux building, what's the format for this?
No such animal that I'm aware of.
There is some rough ordering control using the space/subspace sort keys, but you don't get absolute control over where stuff ends up in memory.
In what ways do you need to control the layout of stuff in memory?
jeff
You probably want to use the same link options as Jason used for the IPL:
-N -R address.
The address specified should match the location where the kernel is loaded into the LIF image. The -N places the $DATA$ section after the $CODE$ section in low memory. The +n option that was being used in the Makefile has the $DATA$ section in the 0x40000000 quadrant. This is wrong for the kernel.
After the kernel is built, take a look at where the sections start in SOM executable. Each section must be copied to its corresponding starting address in the LIF image. Space must be reserved for the bss data if there is a section after it that contains necessary data.
Dave
Quoted 27 lines
After an enormous amount of frustration (with fault only to me, I should have thought that there was a second bootpserver on my network), the kernel tree in CVS actually builds on HPUX. This is really just Jason's work glued into the kernel tree.
Next:
- we need an HPUX ld linker script to resolve the vmlinux building, what's the format for this?
- we need to figure out why the bootloader gives an error when loading the kernel into memory
- Alex
Signature · 7 lines
Alex deVries Vice President of Engineering The Puffin Group --------------------------------------------------------------------------- To unsubscribe: send e-mail to [email protected] with `unsubscribe' as the subject.
Signature · 2 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
In message <[email protected]>you write:
Quoted 4 lines
After the kernel is built, take a look at where the sections start in SOM executable. Each section must be copied to its corresponding starting address in the LIF image. Space must be reserved for the bss data if there is a section after it that contains necessary data.
Right. Use the exec header to find a.out-like boundaries for text, data & bss.
Do not try to build up a memory image using the space/subspace stuff. You'll be bitterly disappointed to find out that the info on the space/subspaces is not wholly accurate in an executable image.
jeff
Quoted 4 lines · Alex deVries
Next:
- we need an HPUX ld linker script to resolve the vmlinux building, what's the format for this?
Thomas Bogendorfer solved this for us.
Quoted 3 lines
- we need to figure out why the bootloader gives an error when loading the kernel into memory
It looks like an IPL problem...
- Alex
Signature · 3 lines
Alex deVries Vice President of Engineering The Puffin Group