mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: 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, eric.y.miao@gmail.com,
	utx@penguin.cz, zaurus-devel@www.linuxtogo.org
Subject: About kernel decompressors (fwd)
Date: Mon, 1 Feb 2010 13:14:56 +0100	[thread overview]
Message-ID: <20100201121454.GA20387@atrey.karlin.mff.cuni.cz> (raw)

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

             reply	other threads:[~2010-02-01 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 12:14 Pavel Machek [this message]
2010-02-01 14:27 ` Eric Miao

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=20100201121454.GA20387@atrey.karlin.mff.cuni.cz \
    --to=pavel@ucw.cz \
    --cc=arminlitzel@web.de \
    --cc=dbaryshkov@gmail.com \
    --cc=eric.y.miao@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=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®