From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Eric Benard <eric@eukrea.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] lib/decompress_unlzo: use fill and full to read and write data
Date: Wed, 23 Feb 2011 18:05:12 +0100 [thread overview]
Message-ID: <20110223170512.GB29927@game.jcrosoft.org> (raw)
In-Reply-To: <4D644DFA.9070706@eukrea.com>
On 00:59 Wed 23 Feb , Eric Benard wrote:
> Hi Jean Christophe,
>
> On 28/01/2011 11:13, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >this will all to simplify the sync with the kernel and later easly add the
> >self decompression support to barebox
> >
> >as example with a lzo compression will reduce barebox from 180224 to 99863
> >bytes so 55.41%
> >-rwxr-xr-x 1 root root 99863 Jan 28 02:17 build/versatilepb/barebox.bin.lzo
> >
> >we also reduce the binary size by 224 bytes
> >
> >Old version
> ># ls -al build/versatilepb/barebox.bin
> >-rwxr-xr-x 1 root root 180468 Jan 28 02:14 build/versatilepb/barebox.bin
> >
> >New version
> ># ls -al build/versatilepb/barebox*
> >-rwxr-xr-x 1 root root 180244 Jan 28 02:13 build/versatilepb/barebox.bin
> >
> >Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD<plagnioj@jcrosoft.com>
>
> unfortunatly, this commit breaks unlzo in barebox :
> unlzo logo.bmp.lzo logo.bmp stays blocked forever
> reverting this commit unbreak the unlzo command.
I try it here on the versatile and it's work fine
I will it again on the sam9261ek and other at91
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-02-23 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 10:13 Jean-Christophe PLAGNIOL-VILLARD
2011-02-22 23:59 ` Eric Benard
2011-02-23 17:05 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2011-02-23 17:21 ` Eric Benard
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=20110223170512.GB29927@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=eric@eukrea.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