All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: sparclinux@vger.kernel.org
Subject: Re: New SILO (was Re: [SOLVED] Take 3: sparc64 CDs work?)
Date: Sun, 20 Jun 2004 19:25:49 +0000	[thread overview]
Message-ID: <20040620192549.GC19634@phunnypharm.org> (raw)
In-Reply-To: <20040620170821.GA19634@phunnypharm.org>

On Sun, Jun 20, 2004 at 12:41:25PM -0700, David S. Miller wrote:
> On Sun, 20 Jun 2004 13:08:22 -0400
> Ben Collins <bcollins@debian.org> wrote:
> 
> > I suspect that in the long run, I really need to make it so that the
> > initrd gets lower memory precendence over the kernel. The kernel itself
> > can be loaded anywhere for sparc64, even in 64-bit address ranges.
> > 
> > But for now, I am about to release SILO 1.4.6 to atleast make this less
> > of a mystery on systems where it fails.
> 
> I have a better idea, remove the 32-bit limitation.
> 
> Create a new HdrS version, add a new member at the end of the bootloader
> header area "sparc_ramdisk_image64", set it to ~0 by default, if the
> bootloader sets it to some non-~0 value, we use it instead of the
> 32-bit limited sparc_ramdisk_image value.

The downside is that I need to load and evaluate the kernel before
loading the initrd in order for it to work. I was already considering
this, but I need to make sure I don't get into a chicken and egg
situation like I did with the feature to load the kernel to a non-zero
location.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/

  reply	other threads:[~2004-06-20 19:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-20 17:08 New SILO (was Re: [SOLVED] Take 3: sparc64 CDs work?) Ben Collins
2004-06-20 19:25 ` Ben Collins [this message]
2004-06-20 19:41 ` David S. Miller

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=20040620192549.GC19634@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=sparclinux@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.