From: Mike Rapoport <mike@compulab.co.il>
To: Alain Knaff <alain@knaff.lu>
Cc: Michael Opdenacker <michael-lists@free-electrons.com>,
Florian Fainelli <florian@openwrt.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-embedded mailing list <linux-embedded@vger.kernel.org>
Subject: Re: Status of bzip2 and lzma kernel compression for ARM?
Date: Mon, 29 Jun 2009 15:21:45 +0300 [thread overview]
Message-ID: <4A48B1D9.90306@compulab.co.il> (raw)
In-Reply-To: <4A478286.8020908@knaff.lu>
Alain Knaff wrote:
> Alain Knaff wrote:
>> Attached is a version of the ARM patch for 2.6.30
>>
>> There seems to be some issues with the include files (which did not pose
>> any problems in 2.6.28...), but hopefully somebody more experienced with
>> the ARM architecture (and with its recent development) than I can help
>> out there.
>>
>> Regards,
>>
>> Alain
>
> Actually, the needed changes turned out to be easier than I initially
> feared. Attached a version that compiles all right.
I gave it a quick test and it hangs before "Decompressing kernel" is output.
I hope I'll have time this week to debug what's wrong there.
> Regards,
>
> Alain
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2009-06-29 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 20:22 Status of bzip2 and lzma kernel compression for ARM? 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 [this message]
2009-06-29 16:39 ` Michael Opdenacker
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=4A48B1D9.90306@compulab.co.il \
--to=mike@compulab.co.il \
--cc=alain@knaff.lu \
--cc=florian@openwrt.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=michael-lists@free-electrons.com \
--cc=thomas.petazzoni@free-electrons.com \
/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