Ollie Lho <[EMAIL PROTECTED]> writes: > Eric W. Biederman wrote: > > > Ollie Lho <[EMAIL PROTECTED]> writes: > > > >>O.K. I found one. But I still got one minor problem: > >> > >>ld -N -Ttext 0x94000 -e _start -o bin32/sis900.elf bin32/ube_start32.o > >>bin32/ube.o bin32/config-sis900.o bin32/sis900.o bin32/pci.o bin32/bootlib.a > >>bin32/bootlib.a(osloader.o): In function `tagged_download': > >>osloader.o(.text+0x9d): undefined reference to `xstart' > >>make: *** [bin32/sis900.elf] Error 1 > >> > >>Any thought ?? > >> > > O.k. Somewhere you have enabled support for etherboot tagged images. > > As these are fundamentally 16bit dos type entities I haven't tried to > > make then work under linuxbios. > > The ELF multiboot format is what to aim for. Next round of patches > > I'll see about a native interface... > > > > > We are having almost everything O.K. But while loading vmlinux (ELF > build by make vmlinux), etherboot says > > (ELF)... segment exceeding memory Unable to load file > > Should we convert the vmlinux to some special ELF file ??
O.k. a raw vmlinux is ELF but it isn't preppared to be loaded by etherboot. The problems are: - It lists it's load virtual address in the physical addres field. Which is why you are having problems. - It doesn't have code to handle parameters as etherboot passes them. If you run mkelfImage on it it tacks on convert_params.c and fixes the kernel to list it's physical load address in the appropriate field. mkelfImage really is just a glorified makefile when you dig into it. Eric
