Hello,
in bitbake.conf we use the maximum lzma compression level (-c -9) for
the initramfs:
IMAGE_CMD_cpio.lzma = "type cpio >/dev/null; cd ${IMAGE_ROOTFS} &&
(find . | cpio -o -H newc | lzma -c -9
>${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.cpio.lzma)
${EXTRA_IMAGECMD}"
This makes decompressor fa
On (10/03/11 10:21), Andrea Adami wrote:
> Hello,
>
> in bitbake.conf we use the maximum lzma compression level (-c -9) for
> the initramfs:
>
> IMAGE_CMD_cpio.lzma = "type cpio >/dev/null; cd ${IMAGE_ROOTFS} &&
> (find . | cpio -o -H newc | lzma -c -9
> >${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.
> I think this is something we can encapsulate in machine.conf files
> so unless the general value in bitbake.conf does not fail for almost
> all cases I would suggest to keep it and instead introduce a new
> variable to control the level
> -Khem
Ok, but then we need a weak assignment in bitbake.c
On Fri, Mar 11, 2011 at 10:49 AM, Andrea Adami wrote:
>> I think this is something we can encapsulate in machine.conf files
>> so unless the general value in bitbake.conf does not fail for almost
>> all cases I would suggest to keep it and instead introduce a new
>> variable to control the level
>
On (11/03/11 10:51), Andrea Adami wrote:
> On Fri, Mar 11, 2011 at 10:49 AM, Andrea Adami wrote:
> >> I think this is something we can encapsulate in machine.conf files
> >> so unless the general value in bitbake.conf does not fail for almost
> >> all cases I would suggest to keep it and instead i
Hello,
I have fixed it in my tree and will send a new patchset tomorrow with
it included.
Cheers,
--
Otavio Salvador O.S. Systems
E-mail: ota...@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
