Re: Pure 64 bootloaders

[Andi Kleen <ak@suse.de>]

Jim Gifford <maillist@jg555.com> writes:

> I have been working on a project to create a Pure 64 bit distro of
> linux, nothing 32 bit in the system. I can accomplish that with no

Hopefully you're using /lib64 for that, otherwise your
packages will be incompatible to everybody else and not 
FHS compliant. If you don't please don't submit any 
patches to hardcode this to upstream packages.

> issues pretty much on all platforms, with the exception of the
> bootloaders. It just seems odd, that all the bootloaders seem to have
> gcc -m32 in their makefiles.

Not only the boot loaders, but the kernel needs a -m32
compilers/toolset to build the bzImage unpacker. There were some plans
to change that, but it hasn't happened so far.
> 
> Silo on the Sparc has gcc -m32
> Grub on the x86 platforms has gcc -m32
>  The only one that builds and works is Lilo, which most people are
> moving away from.
> 
> So for my question, why does a bootloader have to be 32bit?
> Anyone got 64 bit bootloaders for Sparc or x86_64 machines?

kexec is essentially a 64bit boot loader, but you need
linux running before so it has a little bootstrap problem.

I believe the folks at http://www.codegen.com got one too, but
it's proprietary.

The problem is that there is currently no defined protocol
for passing data to the 64bit part of the kernel, so while
it would be possible to write a boot loader that starts
a 64bit kernel it would be very kernel version dependent.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/