Re: [RESEND] bitbake.conf: fix ubi images creation

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2011-09-02 at 18:09 +0200, Denis Carikli wrote:
> Without that commit ubinize.cfg lack a volume name value,
>   and the related ubinize.cfg line looks like that:
>     vol_name=
>   which result in a broken ubi image,which after beeing flashed produce
>   the following error:
>     UBI error: vtbl_check: volume table check failed: record 0, error 11
>   wich result in a kernel panic because the rootfs can't be mounted.
> 
> Signed-off-by: Denis Carikli <denis@eukrea.com>
> ---
>  meta/conf/bitbake.conf |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index a68be07..14ee90c 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -382,6 +382,8 @@ IMAGE_BASENAME = "${PN}"
>  IMAGE_NAME = "${IMAGE_BASENAME}-${MACHINE}-${DATETIME}"
>  IMAGE_LINK_NAME = "${IMAGE_BASENAME}-${MACHINE}"
>  
> +UBI_VOLNAME ?= "${MACHINE}-rootfs"
> +
>  # This option allows for a percentage overage of the actual image size rather than a
>  # fixed extra space, this is space needed for initial startup and basic operations.
>  IMAGE_OVERHEAD_FACTOR ?= 1.3

Merged to master but I moved this definition to image_types.bbclass
since thats the only place its used and we may as well not pollute the
global data store when we don't need to.

Cheers,

Richard