[LinuxBIOS] Patch for vmlinux amd64 with mkelfImage

yhlu yinghailu at gmail.com
Sun Nov 5 04:21:29 CET 2006

for x86_64 there will be vmlinux and bzImage.
current vmlinux entry point is startup_32,
bzImage will be in elf64, and together with vmlinux will not have startup_32.

So we must use 64bit boot loader. Do we have 64bit boot loader except kexec?

but question is for AP, you will still need from
16bit(trampoline.S)-->32bit(startup_32 in head.S )-->64bit (startup_64
in head.S).

are you going to move startup_32 to trampoline.S?


On 11/4/06, Eric W. Biederman <ebiederm at xmission.com> wrote:
> yhlu <yinghailu at gmail.com> writes:
> > On 11/4/06, Eric W. Biederman <ebiederm at xmission.com> wrote:
> >> >
> >> > Then you will need 64bit boot loader.
> >>
> >> If you are booting vmlinux yes.
> >
> > Wow? what happened?
> Nothing.  That is just where it looks like vmlinux on x86_64 is going.
> There are two separate conversations to take it there.
> >> > Or can I use entrypoint for start64-0x100 to get the address for start32
> >>
> >> Nope.  The code will go 64bit in the decompresser.
> >
> > vmlinux should not include decompressor. or vmlinux will become vmlinuz?
> The standard thing to boot is bzImage.
> Like I said the 32bit entry point is really not supported for vmlinux on x86_64
> please don't count on it being there.
> bzImage will shortly also become ELF but that is another story...
> Eric

More information about the coreboot mailing list