From: bmpenrod@endruntechnologies.com (Bruce M. Penrod)
To: linux-arm-kernel@lists.infradead.org
Subject: Maximum bootable kernel size in current ARM linux
Date: Tue, 14 Sep 2010 10:55:40 -0700 [thread overview]
Message-ID: <4C8FB71C.8010208@endruntechnologies.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1009141330230.19366@xanadu.home>
Nicolas Pitre wrote:
> On Mon, 13 Sep 2010, Bruce M. Penrod wrote:
>
>>
>> Russell King - ARM Linux wrote:
>>> On Mon, Sep 13, 2010 at 12:40:56AM -0700, Bruce M. Penrod wrote:
>>>> This seems like a pretty straightforward question, but extensive web
>>>> searching hasn't shown a really clear, up-to-date answer. The most
>>>> recent info is circa 2004 and states that 4MB is the largest uncompressed
>>>> ARM kernel that may be loaded. Not being an ARM assembly guru (head.S
>>>> baffles me), I'd like to know if that is still true in 2010, and if it
>>>> is, why?
>>> It is no longer true; the only limit now is the size of contiguous RAM
>>> to fit the kernel image into.
>>>
>> Interesting. I finally was able to get an uncompressed kernel a little below
>> 4MB, and now it boots. I'm working with 2.6.35rc6 on an OpenRD Ultimate
>> (Marvell Kirkwood) with Slackware, doing native compiles. I'm wondering if
>> there could be any problem with U-Boot for larger kernels than 4MB, but it
>> doesn't complain and says that it is copying the image. The symptom I had
>> with a much larger kernel (~15MB) is a total hang, not even "Uncompressing
>> linux".
>>
>> I'll add some innocuous stuff back in until I get above 4MB again and see if
>> it breaks again.
>
> When it breaks, do you still see the "Uncompressing Linux... done,
> booting the kernel." message?
>
>
> Nicolas
>
I think it depended upon how "too big" the kernel was. With one only
slightly larger than 4 MB, I did see "Uncompressing Linux...", but not
"done, booting the kernel." With a very large kernel (15MB), nothing
printed at all.
I have not retested since successfully booting one slightly smaller than
4096 * 1024. When I do, I will post the results. Should happen today.
--
Bruce
next prev parent reply other threads:[~2010-09-14 17:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 7:40 Maximum bootable kernel size in current ARM linux Bruce M. Penrod
2010-09-13 8:43 ` Marek Vasut
2010-09-13 9:56 ` Haojian Zhuang
2010-09-13 10:10 ` Simon Guinot
2010-09-13 10:15 ` Russell King - ARM Linux
2010-09-13 11:58 ` Matthieu CASTET
2010-09-13 12:38 ` Russell King - ARM Linux
2010-09-14 12:35 ` Dave P. Martin
2010-09-14 12:54 ` Catalin Marinas
2010-09-14 17:37 ` Nicolas Pitre
2010-09-16 17:16 ` Catalin Marinas
2010-09-16 17:51 ` Russell King - ARM Linux
2010-09-16 18:37 ` Nicolas Pitre
2010-09-17 10:09 ` Catalin Marinas
2010-09-16 17:58 ` Nicolas Pitre
2010-09-17 10:09 ` Catalin Marinas
2010-09-13 10:01 ` Russell King - ARM Linux
2010-09-13 19:43 ` Bruce M. Penrod
2010-09-14 17:32 ` Nicolas Pitre
2010-09-14 17:55 ` Bruce M. Penrod [this message]
2010-09-14 18:46 ` Nicolas Pitre
2010-09-15 20:30 ` Bruce M. Penrod
2010-09-15 22:02 ` Alexander Clouter
2010-09-15 22:19 ` Nicolas Pitre
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=4C8FB71C.8010208@endruntechnologies.com \
--to=bmpenrod@endruntechnologies.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).