[RFC PATCH] Increasing the max_leb_count

[RFC PATCH] Increasing the max_leb_count

[Karthik Ramanan]

Background:

* GLSDK brings in a lot of multimedia and graphics
  enabling components as well as example applications.
* Customers are going to add more software layers on top 
  of this to enable more feature rich graphics and multimedia. 
* There are two configurations that are used internally:
   ** Release filesystem
   ** Debug filesystem - (Release + GDB + dbg-pkgs)
      dbg-pkgs is basically the EXTRA_MACHINE_FEATURES in 
      the local.conf that brings in the sources and debug
      symbols to allow gdb debugging.

With the current leb_count it is not possible to support 
the above usecases. And to allow for enough room for the 
customer to add their components and not hit the space 
issue, it is proposed to make this change.

Karthik Ramanan (1):
  dra7xx-evm: ubifs: Increase "max_leb_cnt"

 conf/machine/dra7xx-evm.conf |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
1.7.9.5

[RFC PATCH] Increasing the max_leb_count

[Karthik Ramanan]

Background:

* GLSDK brings in a lot of multimedia and graphics
  enabling components as well as example applications.
* Customers are going to add more software layers on top 
  of this to enable more feature rich graphics and multimedia. 
* There are two configurations that are used internally:
   ** Release filesystem
   ** Debug filesystem - (Release + GDB + dbg-pkgs)
      dbg-pkgs is basically the EXTRA_MACHINE_FEATURES in 
      the local.conf that brings in the sources and debug
      symbols to allow gdb debugging.

With the current leb_count it is not possible to support 
the above usecases. And to allow for enough room for the 
customer to add their components and not hit the space 
issue, it is proposed to make this change.

Karthik Ramanan (1):
  dra7xx-evm: ubifs: Increase "max_leb_cnt"

 conf/machine/dra7xx-evm.conf |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
1.7.9.5

[RFC PATCH] dra7xx-evm: ubifs: Increase "max_leb_cnt"

[Karthik Ramanan]

    * This is need to allow some room for customers to build on top
      of the filesystem that we support 
    * This is needed for larger filesystem size to support dev image.

Signed-off-by: Karthik Ramanan <a0393906@ti.com>
---
 conf/machine/dra7xx-evm.conf |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/dra7xx-evm.conf b/conf/machine/dra7xx-evm.conf
index 175450f..3b88668 100644
--- a/conf/machine/dra7xx-evm.conf
+++ b/conf/machine/dra7xx-evm.conf
@@ -23,7 +23,7 @@ UBOOT_MACHINE = "dra7xx_evm_config"
 # UBI: logical eraseblock size:    126976 bytes
 # from ubiattach stdout:
 # UBI device number 0, total 1988 LEBs
-MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 4352"
+MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 5120"
 
 # do ubiattach /dev/ubi_ctrl -m 7 -O 2048
 # from dmesg:
-- 
1.7.9.5

Re: [RFC PATCH] Increasing the max_leb_count

[Denys Dmytriyenko]

Vivek, Jake,

I suggested that Karthik sends an RFC to get your input on this matter. My 
concern is that we have large enough flash and enough storage space left for 
anything else you might want to store (e.g. backup/recovery images, etc.)

Please provide your feedback for this patch. Thanks.

-- 
Denys


On Wed, Jan 21, 2015 at 11:22:48PM +0530, Karthik Ramanan wrote:
> Background:
> 
> * GLSDK brings in a lot of multimedia and graphics
>   enabling components as well as example applications.
> * Customers are going to add more software layers on top 
>   of this to enable more feature rich graphics and multimedia. 
> * There are two configurations that are used internally:
>    ** Release filesystem
>    ** Debug filesystem - (Release + GDB + dbg-pkgs)
>       dbg-pkgs is basically the EXTRA_MACHINE_FEATURES in 
>       the local.conf that brings in the sources and debug
>       symbols to allow gdb debugging.
> 
> With the current leb_count it is not possible to support 
> the above usecases. And to allow for enough room for the 
> customer to add their components and not hit the space 
> issue, it is proposed to make this change.
> 
> Karthik Ramanan (1):
>   dra7xx-evm: ubifs: Increase "max_leb_cnt"
> 
>  conf/machine/dra7xx-evm.conf |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> -- 
> 1.7.9.5
> 
> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

Re: [RFC PATCH] Increasing the max_leb_count

[Chengalvala, Vivek]

[-- Attachment #1: Type: text/plain, Size: 5825 bytes --]

Karthik, Denys,



Jake is currently out on vacation and will be back next week. Back in November, we started to see build failures creating the tisdk-rootfs, specifically when making the UBI filesystem because of max_leb_cnt.

Hence, Jake picked a value that was slightly greater than the reported minimum size required. The proposal to increase it to 5120 looks fine.



Regards,

Vivek





For am57xx-evm, (http://gtjenkins.itg.ti.com/nightly_builds/mcsdk-8.0.x/134-2014-11-25_20-40-31/artifacts/output/results/build-2014-11-25_22-20-58/log-files/am57xx-evm-error-logs/tisdk-rootfs-image_1.0-r0_do_rootfs.log) :



NOTE: The image creation groups are: [['tar', 'ubi']]

NOTE: Running image creation script for tar: /home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/work/am57xx_evm-oe-linux-gnueabi/tisdk-rootfs-image/1.0-r0/temp/create_image.tar ...

NOTE: Running image creation script for ubi: /home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/work/am57xx_evm-oe-linux-gnueabi/tisdk-rootfs-image/1.0-r0/temp/create_image.ubi ...

ERROR: Error: The image creation script '/home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/work/am57xx_evm-oe-linux-gnueabi/tisdk-rootfs-image/1.0-r0/temp/create_image.ubi' returned 255:

Error: max_leb_cnt too low (3980 needed)

WARNING: /home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/work/am57xx_evm-oe-linux-gnueabi/tisdk-rootfs-image/1.0-r0/temp/create_image.ubi:1 exit 255 from

  mkfs.ubifs -r /home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/work/am57xx_evm-oe-linux-gnueabi/tisdk-rootfs-image/1.0-r0/rootfs -o /home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/deploy/images/am57xx-evm/tisdk-rootfs-image-am57xx-evm-20141126032606.rootfs.ubifs -F -m 2048 -e 126976 -c 3836



DEBUG: Python function do_rootfs finished

ERROR: Function failed: do_rootfs





For dra7xx-evm (http://gtjenkins.itg.ti.com/nightly_builds/mcsdk-8.0.x/134-2014-11-25_20-40-31/artifacts/output/results/build-2014-11-26_00-55-49/log-files/dra7xx-evm-error-logs/tisdk-rootfs-image_1.0-r0_do_rootfs.log) :



NOTE: The image creation groups are: [['tar', 'ubi']]

NOTE: Running image creation script for tar: /home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/work/dra7xx_evm-oe-linux-gnueabi/tisdk-rootfs-image/1.0-r0/temp/create_image.tar ...

NOTE: Running image creation script for ubi: /home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/work/dra7xx_evm-oe-linux-gnueabi/tisdk-rootfs-image/1.0-r0/temp/create_image.ubi ...

ERROR: Error: The image creation script '/home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/work/dra7xx_evm-oe-linux-gnueabi/tisdk-rootfs-image/1.0-r0/temp/create_image.ubi' returned 255:

Error: max_leb_cnt too low (4156 needed)

WARNING: /home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/work/dra7xx_evm-oe-linux-gnueabi/tisdk-rootfs-image/1.0-r0/temp/create_image.ubi:1 exit 255 from

  mkfs.ubifs -r /home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/work/dra7xx_evm-oe-linux-gnueabi/tisdk-rootfs-image/1.0-r0/rootfs -o /home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/deploy/images/dra7xx-evm/tisdk-rootfs-image-dra7xx-evm-20141126060210.rootfs.ubifs -F -m 2048 -e 126976 -c 3836



DEBUG: Python function do_rootfs finished

ERROR: Function failed: do_rootfs







-----Original Message-----
From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of Dmytriyenko, Denys
Sent: Wednesday, January 21, 2015 1:59 PM
To: R, Karthik
Cc: meta-ti@yoctoproject.org
Subject: Re: [meta-ti] [RFC PATCH] Increasing the max_leb_count



Vivek, Jake,



I suggested that Karthik sends an RFC to get your input on this matter. My concern is that we have large enough flash and enough storage space left for anything else you might want to store (e.g. backup/recovery images, etc.)



Please provide your feedback for this patch. Thanks.



--

Denys





On Wed, Jan 21, 2015 at 11:22:48PM +0530, Karthik Ramanan wrote:

> Background:

>

> * GLSDK brings in a lot of multimedia and graphics

>   enabling components as well as example applications.

> * Customers are going to add more software layers on top

>   of this to enable more feature rich graphics and multimedia.

> * There are two configurations that are used internally:

>    ** Release filesystem

>    ** Debug filesystem - (Release + GDB + dbg-pkgs)

>       dbg-pkgs is basically the EXTRA_MACHINE_FEATURES in

>       the local.conf that brings in the sources and debug

>       symbols to allow gdb debugging.

>

> With the current leb_count it is not possible to support

> the above usecases. And to allow for enough room for the

> customer to add their components and not hit the space

> issue, it is proposed to make this change.

>

> Karthik Ramanan (1):

>   dra7xx-evm: ubifs: Increase "max_leb_cnt"

>

>  conf/machine/dra7xx-evm.conf |    2 +-

>  1 file changed, 1 insertion(+), 1 deletion(-)

>

> --

> 1.7.9.5

>

> --

> _______________________________________________

> meta-ti mailing list

> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>

> https://lists.yoctoproject.org/listinfo/meta-ti

--

_______________________________________________

meta-ti mailing list

meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>

https://lists.yoctoproject.org/listinfo/meta-ti

[-- Attachment #2: Type: text/html, Size: 12014 bytes --]