From: Robert Reif <reif@earthlink.net>
To: sparclinux@vger.kernel.org
Subject: Re: SILO & Ext4
Date: Fri, 05 Jun 2009 02:49:25 +0000 [thread overview]
Message-ID: <4A2887B5.8070308@earthlink.net> (raw)
In-Reply-To: <a4423d670906010333x16cbae69g667a7441be2f140a@mail.gmail.com>
David Miller wrote:
> From: Robert Reif <reif@earthlink.net>
> Date: Wed, 03 Jun 2009 07:22:36 -0400
>
>
>> David Miller wrote:
>>
>>> The limit is now at 64MB on sparc64, isn't that enough?
>>>
>>>
>> And what is the limit on sparc32?
>>
>
> I have no idea, to be honest with you.
>
>
It looks like it's between 2.4 and 2.6 MB depending on
the source.
I found a 2 year old patch to silo that loads the kernel
above 4 MB like sparc64 but the sparc32 kernel is not
relocatable. It loads fine but then tries to move it down
low where it wants to be and fails because there isn't
enough space.
SILO Version 1.4.14
boot:
Allocated 64 Megs of memory at 0x3FFFC000 for kernel
Uncompressing image...
Your kernel cannot fit into the memory destination. This
can be resolved by recompiling the kernel with more devices
built as modules, or upgrading your kernel to one that
supports being loaded to higher memory areas (currently
2.6.3+ or 2.4.26+).
boot:
I'm looking at head_32.S and head_64.s to try and figure
out what's involved in making sparc32 relocatable but I'm
not sure what to look for. Any hints?
next prev parent reply other threads:[~2009-06-05 2:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 10:33 SILO & Ext4 Alexander Beregalov
2009-06-01 10:33 ` Alexander Beregalov
2009-06-01 10:41 ` David Miller
2009-06-01 10:41 ` David Miller
2009-06-01 13:53 ` Alex Buell
2009-06-01 13:53 ` Alex Buell
2009-06-01 10:43 ` Alex Buell
2009-06-01 10:43 ` Alex Buell
2009-06-03 1:29 ` Robert Reif
2009-06-03 3:33 ` David Miller
2009-06-03 11:22 ` Robert Reif
2009-06-03 22:00 ` David Miller
2009-06-05 2:49 ` Robert Reif [this message]
2009-06-05 7:46 ` David Miller
2009-06-05 12:12 ` Robert Reif
2009-06-06 0:41 ` David Miller
2009-06-08 0:01 ` Mark Fortescue
-- strict thread matches above, loose matches on Subject: below --
2009-09-03 9:54 David 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=4A2887B5.8070308@earthlink.net \
--to=reif@earthlink.net \
--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.