From: tbm@cyrius.com (Martin Michlmayr)
To: linux-arm-kernel@lists.infradead.org
Subject: Status of bzip2 and lzma kernel compression for ARM?
Date: Wed, 11 Nov 2009 17:20:35 +0000 [thread overview]
Message-ID: <20091111172035.GA9682@deprecation.cyrius.com> (raw)
In-Reply-To: <20091111170729.GG2605@pc-ran3241.res.insa>
* Albin Tonnerre <albin.tonnerre@free-electrons.com> [2009-11-11 18:07]:
> Regarding Bzip2, some testing showed that the decompressor needs at least 3.5Mb
> of memory available for malloc(), which is not available on ARM as head.S
> allocates only 64kb, so I'm sure what to do about it. At this stage, I think
> the most sensible thing to do is forgetting about using bzip2 on ARM.
I'm mostly interested in LZMA, so lack of bzip2 support would not be a
problem for me.
> The LZMA patch relies on patch 2/4 of the LZO patchset, which I
> resubmitted today: http://lkml.org/lkml/2009/11/11/129 I'll likely
> submit the LZMA patch once I get Russell's approval on the ARM part
> of the LZO patchset. In the
Excellent! I'll give your patch a go on the weekend.
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2009-11-11 17:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 16:34 Status of bzip2 and lzma kernel compression for ARM? Martin Michlmayr
2009-11-11 17:07 ` Albin Tonnerre
2009-11-11 17:20 ` Martin Michlmayr [this message]
2009-11-12 8:45 ` Alain Knaff
-- strict thread matches above, loose matches on Subject: below --
2009-06-24 20:22 Michael Opdenacker
2009-06-24 20:22 ` Michael Opdenacker
2009-06-25 8:56 ` Mike Rapoport
2009-06-25 9:04 ` Florian Fainelli
2009-06-25 15:24 ` Michael Opdenacker
2009-06-25 17:08 ` Paul Mundt
2009-06-28 13:57 ` Alain Knaff
2009-06-28 14:47 ` Alain Knaff
2009-06-29 12:21 ` Mike Rapoport
2009-06-29 16:39 ` Michael Opdenacker
2009-07-03 15:43 ` Albin Tonnerre
2009-07-03 15:43 ` Albin Tonnerre
2009-07-13 19:17 ` Albin Tonnerre
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=20091111172035.GA9682@deprecation.cyrius.com \
--to=tbm@cyrius.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 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.