From: Jeff Garzik <jgarzik@pobox.com>
To: Jim Gifford <maillist@jg555.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Pure 64 bootloaders
Date: Sat, 10 Sep 2005 03:52:36 -0400 [thread overview]
Message-ID: <20050910075235.GA28321@havoc.gtf.org> (raw)
In-Reply-To: <43228E4E.4050103@jg555.com>
On Sat, Sep 10, 2005 at 12:42:06AM -0700, Jim Gifford wrote:
> 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
> 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.
>
> 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?
> Are there technical limitations that bootloaders can't be 64 bit?
> If we can't have a pure64 environment, why does the Kernel support it?
It depends on the mode the CPU is in, at boot time. Also, there are size
constraints, as 64-bit code is usually larger.
There's nothing stopping you from writing a bootloader that immediately
put the CPU into 64-bit mode, and then proceeds from there...
Jeff
next prev parent reply other threads:[~2005-09-10 7:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 7:42 Jim Gifford
2005-09-10 7:52 ` Jeff Garzik [this message]
2005-09-10 8:01 ` David S. Miller
2005-09-11 16:33 ` Jim Gifford
2005-09-11 18:48 ` David S. Miller
2005-09-11 18:49 ` David S. Miller
2005-09-10 8:28 ` Andi Kleen
2005-09-10 8:39 ` Jeff Garzik
2005-09-10 16:34 ` Chris Wedgwood
2005-09-10 18:15 ` David S. Miller
2005-09-12 21:32 ` Joe Bob Spamtest
2005-09-12 21:41 ` David S. Miller
2005-09-12 22:02 ` Joe Bob Spamtest
2005-09-12 22:12 ` David S. Miller
2005-09-12 23:09 ` Joe Bob Spamtest
2005-09-13 16:52 ` Lennart Sorensen
2005-09-13 17:00 ` Joe Bob Spamtest
2005-09-14 3:44 ` Kyle Moffett
2005-09-14 13:20 ` Lennart Sorensen
2005-09-14 17:26 ` Kyle Moffett
2005-09-13 17:21 ` Maciej W. Rozycki
2005-09-13 19:37 ` Lennart Sorensen
2005-09-14 9:39 ` Maciej W. Rozycki
2005-09-10 18:30 ` Harald Dunkel
2005-09-12 14:50 ` Roger Heflin
2005-09-13 17:14 ` Bastian Blank
2005-09-15 6:16 ` Harald Dunkel
2005-09-11 11:53 ` Stephen Frost
2005-09-11 14:14 ` Stefan Smietanowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050910075235.GA28321@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maillist@jg555.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®