From: Eric Miao <eric.y.miao@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: rpurdie@rpsys.net, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
arminlitzel@web.de, Cyril Hrubis <metan@ucw.cz>,
thommycheck@gmail.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
dbaryshkov@gmail.com, omegamoon@gmail.com, utx@penguin.cz,
zaurus-devel@www.linuxtogo.org
Subject: Re: About kernel decompressors (fwd)
Date: Mon, 1 Feb 2010 22:27:27 +0800 [thread overview]
Message-ID: <f17812d71002010627u795ff155l62c96bf64240b584@mail.gmail.com> (raw)
In-Reply-To: <20100201121454.GA20387@atrey.karlin.mff.cuni.cz>
It sounds to me like this is because of the 1.4M (cannot
remember the exact size) constraint of the kernel size
on NAND that the bootloader is able to load?
On Mon, Feb 1, 2010 at 8:14 PM, Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
>
> I guess Andrea wanted me to forward this....
>
> ----- Forwarded message from Andrea Adami <andrea.adami@gmail.com> -----
> Date: Mon, 1 Feb 2010 13:08:44 +0100
> From: Andrea Adami <andrea.adami@gmail.com>
> To: pavel@ucw.cz
> Subject: About kernel decompressors
>
> Pavel,
>
> I'd like to add a couple of observations in the "Uncompressing broken
> with commit e7db7b4270" thread.
> Unfortunately I wasn't subscribed and I can't properly reply to the thread...
>
> This is for kernels 2.6.33-rc5 and -rc6 on Sharp corgi (Zaurus
> SL-C860, pxa255, 64M RAM)
>
> 1) after that commit neither gzip, nor lzo can decompress from NAND
> 2) I tested the LZMA patch and this also won't help the boot from nand
> 3) kernel size is uninfluent: I tested 930KiB-lzma kernels and 1240KiB
> gzip-kernels.
> 4) I tried to set stack size to 8192, still no boot
>
> 5) all the 3 above kernels boot just fine from kexec (I launch them
> with linux-kexecboot-2.6.26)
>
> >From nand, the boot stops immediately after
> **** JUMP to LINUX! ****
>
>
> Cheers
>
> Andrea
>
> ----- End forwarded message -----
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
>
prev parent reply other threads:[~2010-02-01 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 12:14 Pavel Machek
2010-02-01 14:27 ` Eric Miao [this message]
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=f17812d71002010627u795ff155l62c96bf64240b584@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=utx@penguin.cz \
--cc=zaurus-devel@www.linuxtogo.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
all inboxes | Powered by JetHome®