I don't often do this, but I just read a white paper by Benjamin Zores on the relationship between Android and traditional embedded Linux, that I thought was quite good. It's a bit of a subtle

Hi, In the last Japan Jamboree, many attendees pointed out the inconvenience of non accessibility of the old CE Linux Forum wiki which had been troubled due to some technical reason. Now it is

Hi, I uploaded the videos of the last Jamboree sessions. Some of them were performed in English. They will be informative for non Japanese speakers as

Hello, Sorry for the inconvenience regarding changelog. Another patch(v4) is not required so this is the information you mentioned. I'm not sure that I captured what we had discussed regarding all

Hi, It is tomorrow, March 8th! http://elinux.org/Japan_Technical_Jamboree_44 See you soon! ----- JAPANESE

That looks like on overkill to me, besides I don't think that's the purpose of tools/. Maybe everyone who wants to test this, should install the tool and go wild without disturbing the

If we want to have more coverage, how about importing the lz4demo utility source code to tools/lz4/, and change scripts/Makefile.lib to point at it? Once the lz4 utilities have reached a broader

Ok, I will update it as soon as the patch set is stabilized. Thanks, Kyungsik

Sorry, It will have all the information you mentioned. I can reply to this thread if you want. Or I might need another patch(v4). I have one thing to be confirmed regarding LZ4 format. One of the

Yes, that's a showstopper even for linux-next. What a shame. It means this code will walk into mainline with practically zero third-party testing. Oh well, the risk is minor. If it breaks,

What happened to the changelog? The earlier version at least had some rudimentary benchmarking results, but now we don't even have that. Someone should prepare the information explaining why we

Please add the new magic to Documentation/x86/boot.txt as well. Kyungsik Lee <kyungsik.lee@...> wrote: -- Sent from my mobile phone. Please excuse brevity and lack of formatting.

I'm ok with this only if the patch is clearly marked LINUS DO NOT MERGE. Kyungsik Lee <kyungsik.lee@...> wrote: -- Sent from my mobile phone. Please excuse brevity and lack of formatting.

Hello, I do not think making this the default is good idea, because the lz4demo utility that you need to actually compress the kernel (used in patch 2) is not installed nor available by default on

Do I understand it correctly that when this thing gets committed, kernel builds on all systems missing the lz4 tool will fail and everybody should go running to get it so that everybody can build

This patch makes x86 and arm kernels default to the LZ4-compressed to test new LZ4 code in the linux-next. This is requested by Andrew Morton. Signed-off-by: Kyungsik Lee <kyungsik.lee@...> ---

This patch integrates the LZ4 decompression code to the x86 pre-boot code. And it depends on two patchs below lib: Add support for LZ4-compressed kernel decompressor: Add LZ4 decompressor

This patch integrates the LZ4 decompression code to the arm pre-boot code. And it depends on two patchs below lib: Add support for LZ4-compressed kernel decompressor: Add LZ4 decompressor

This patch adds support for extracting LZ4-compressed kernel images, as well as LZ4-compressed ramdisk images in the kernel boot process. This depends on the patch below decompressor: Add LZ4

This patch adds support for LZ4 decompression in the Linux Kernel. LZ4 Decompression APIs for kernel are based on LZ4 implementation by Yann Collet. LZ4 homepage :