[meta-freescale] [PATCH 2/5] imx-base.inc, mxs-base.inc: Stop generating tar.bz2 image tarball by default

Otavio Salvador otavio.salvador at ossystems.com.br
Thu Sep 24 04:46:48 PDT 2015

Hello Igor,

On Thu, Sep 24, 2015 at 5:49 AM, Igor Grinberg <grinberg at compulab.co.il> wrote:
> On 09/22/15 15:46, Otavio Salvador wrote:
>> The tar.bz2 is useful for people using NFS or generating the SD card
>> image byhand, those can enable this in the board file or in the
>> local.conf when needed. By the fault the SD card image should be the
>> only image built as it is the most commonly used one for initial
>> development.
> It is also useful for uniform deployment, when you do not know which
> storage is going to be used for rootfs. For example you can provide
> the tar.bz2 for deployment on any device, e.g. NAND, SD card, mSATA...
> Although it will require another form of deployment technique (not dd),
> but I think it is still useful.
> On the other hand, I agree that it can be enabled in the board file or
> the local.conf.
> So, you decide...

Yes, I agree that the tar.bz2 is very useful however this should be
handled by machine.

Machines wishing to have this enabled, can do it setting the variable
in the machine file.

The imx-base.inc should be trimmed and in fact this setting should be
set on all machine files as it is really a machine option, however the
default set of images generated ought to be well thought as it has
impact on:

- build time
- storage use

Both are important, specially for autobuilders[1] as we need to cover
many machines to try to keep the quality of the BSP high.

1. http://ci.ossystems.com.br/

Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

More information about the meta-freescale mailing list