On Sun, Aug 27, 2000 at 07:19:49PM +0200, Harald Koerfgen wrote:
>
> The PROM knows nothing about partitions or such so these extends refer
> obviously to the start of the disk.
>
Good
>
> Yes. "mipsel-linux-objcopy --output-target=binary" is your friend.
>
Even worse ...
Compilation - Relocation - Stripping -
start.b: start.r
objcopy --remove-section=.bss \
--remove-section=.data \
--remove-section=.reginfo \
--remove-section=.mdebug \
--output-target=binary start.r start.b
start.r: start.o
ld -Ttext=0x80020000 -Tdata=0x80020000 -Tbss=0x80020000 \
start.o -o start.r
start.o: start.S
gcc -fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -c start.S
> > 4. Does the MS-DOS disklabel and the DEC bootblock interfer in any
> > kind that its impossible to have a diskloader with MS-DOS Disklabels
>
> No, that should work as long as the the the boot map is short enough not to
> overwrite the partition information.
>
Does that mean that the limit of the boot_map in the bootprep
is arbitrary and the DEC firmware bootloader would continue
read/process boot_maps in the whole first block ?
> I have successfully booted Linux kernels with bootprep. Depending on
> the code you want to load, for example a second stage bootloader, you
> may need to adjust "boot_block->loadAddr" and "boot_block->execAddr".
Yep - I guessed so - loadAddr hasnt changed but i guess execAddr
needs to point to kernel_entry ...
> > I thought of a bootloader much like the silo - Capable of reading
> > an ext2 filesystem via libext2 etc.
>
> That's what I always wanted to do but I never found the time...
:) - Well see - I got someone else i donated a Decstation to
whom i gave the first goal of writing a boot loader for the donation :)
The problem right now which i have is that i cant seem to load
ANYTHING - Not raw instructions not elf not ecoff - Even simplest
instruction like a tight loop (Wouldnt go back into prom)
dont seem to get executed.
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
"Write only memory - Oops. Time for my medication again ..."
|