All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Gifford <maillist@jg555.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Pure 64 bootloaders
Date: Sun, 11 Sep 2005 09:33:26 -0700	[thread overview]
Message-ID: <43245C56.5000905@jg555.com> (raw)
In-Reply-To: <20050910.010114.28468998.davem@davemloft.net>

David S. Miller wrote:

>You can make SILO 64-bit, but it would just be a lot
>of work and would just result in a SILO that, unlike
>current SILO, would only work on UltraSPARC machines.
>
>There really is no advantage, and known disadvantages, to
>making SILO 64-bit.
>  
>
If I have a system that is a Pure64 environment, I try to compile Silo, 
it will not function. Since there is no support for 32 bit, how would I 
be able to use it.

Isn't there a way to compile the programs necessary as 64bit but the 
actual mbr or .b files depending on your architecture be 32 bit. I

In the case of Silo, it compiles, but when you run silo -f, when you 
reboot, it Starts Silo, then gives, Program Terminiated in OBP. Which 
now makes the computer useless, unless you have a 32 bit build of silo 
standing around.

Also in the case of Silo, if you try to compile it on a modern tool 
chain, the .b files it generates don't work, which I have reported 
upstream. Modern toolchain = binutils 2.16.1, gcc 3.4.4, and glibc 2.3.5.

For the Sparc64 builds, I'm starting to look at using OBP to do the booting.

-- 
----
Jim Gifford
maillist@jg555.com


  reply	other threads:[~2005-09-11 16:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10  7:42 Pure 64 bootloaders Jim Gifford
2005-09-10  7:52 ` Jeff Garzik
2005-09-10  8:01 ` David S. Miller
2005-09-11 16:33   ` Jim Gifford [this message]
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=43245C56.5000905@jg555.com \
    --to=maillist@jg555.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.