All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: sparclinux@vger.kernel.org
Subject: SILO 1.4.0 released
Date: Wed, 28 Jan 2004 17:10:24 +0000	[thread overview]
Message-ID: <20040128171024.GV532@phunnypharm.org> (raw)

After many weeks of bugging the shit out of Dave for help, I've finally
finished the SILO support for loading kernels into arbitrary places in
memory.  What does this mean for all of you? It means it extends the
current limit of kernel image sizes from 3.5Megs to the theoretical
8Megs that the kernel actually supports.

Two cavaets:

1) You need to wait for Dave to pull my kernel changes needed for this
   to work (the kernel needed some work to be able to run from someplace
   other than the physical base of the memory).

2) Currently images > 4Megs fail at some point in the kernel
   initialization. Something goes screwy when a function in the lower
   4Megs tries to access data in the upper 4Megs. The kernel locks two
   4Meg TLB's in the case where the kernel is > 4Megs. Something is
   broken though, and I may need Dave to look at it, since it's beyond
   my understanding at this point.

This only works on sparc64. Someone else can look at the changes I did
in SILO and do something similar for sparc32. You'll likely have to mess
with the kernel (again, wait for Dave to get my changes, and you can
look at those).

WARNING: I need to retest initrd support for sparc64 in the current
SILO, because I changed the way it allocated memory for the kernel and
initrd.  DO NOT consider this SILO stable enough for anything other than
testing at this point.

Even though you don't have the changes for the kernel, I'd appreciate if
people could test this SILO to make sure it works with current setups. I
don't want to break anything running kernels that don't support being
loaded to higher memory. I tested this on my U5, U2, SB100, U30 and
E3000. That's close to most types of machines, but it ain't the end all
to make me sleep better.

So, for the tarball and a binary build of the loaders:

http://www.sparc-boot.org/pub/silo/

If you don't want to compile it, just get the silo-loaders package,
unpack second.b into /boot/ and run "silo -f". Nothing has changed in
the first stage loaders, so you don't have to have the same version.

-- 
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-01-28 17:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040128171024.GV532@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.