1. 03 Nov, 2013 1 commit
  2. 28 Oct, 2013 1 commit
    • Christopher Larson's avatar
      fsl-eula-unpack: add FSL_EULA_FILE to vardepsexclude · 0b808d44
      Christopher Larson authored
      FSL_EULA_FILE is defined with :=, which means it contains a full absolute path
      to the layer directory. If this is allowed to make it into the task checksum,
      it becomes impossible to use the shared states for these recipes without
      having meta-fsl-arm in the exact same path in the filesystem it was in when
      the sstate archives were created. Add FSL_EULA_FILE to
      do_unpack[vardepsexclude].
      Signed-off-by: default avatarChristopher Larson <kergoth@gmail.com>
      0b808d44
  3. 25 Sep, 2013 1 commit
    • Otavio Salvador's avatar
      fsl-dynamic-packagearch.bbclass: Dynamically set package architecture · 21d99526
      Otavio Salvador authored
      This allow to easy reuse of binary packages among similar SoCs. The
      usual use for this is to share SoC specific packages among different
      boards. The class can be used to share GPU packages for i.MX53 boards
      (as all them share the AMD GPU) and i.MX6 based boards (as all them
      share Vivante GPU).
      
      It inspects the database and identify if the package provides or
      depends on one of subarch provided values and if it does, it sets the
      PACKAGE_ARCH for MACHINE_SUBARCH value otherwise if it matches in the
      machine specific filter, it sets it to MACHINE_ARCH.
      
      This reduces the amount of packages we build, for example in case of
      core-image-x11 we:
      
      $ ls -l tmp/deploy/rpm/cortexa9hf_vfp_neon_mx6/*.rpm | wc -l
      75
      
      So we reuse 75 binaries; these would be build otherwise.
      
      It being dynamically set or statically set it has following benefits:
      
      * correctness: it is easier to ensure the system behaves as expected
      * correctness for non-tracked recipes: new recipes, if depending on
        virtual/kernel or GPU has the right architecture choosen, without a
        .bbappend file for them
      * safeness: non-expert users get a more adequate behavior as the
        complexity of choosing the right architecture is simplified for them
      * easy maintenance: it is easier for me, as maintainer, to maintain a
        code which decides what to do than having hundreds of bbappend files
        for it
      
      Change-Id: Icb0a8060e862c8eeb166c45d1b39c40de07b01d8
      Signed-off-by: default avatarOtavio Salvador <otavio@ossystems.com.br>
      21d99526
  4. 29 Aug, 2013 1 commit
  5. 29 Jul, 2013 1 commit
  6. 24 Apr, 2013 1 commit
  7. 26 Mar, 2013 1 commit
  8. 07 Mar, 2013 1 commit
    • Otavio Salvador's avatar
      image_types_fsl.bbclass: Fix deploy of mxsboot-sdcard image · c64d5870
      Otavio Salvador authored
      The mxsboot-sdcard image is the current way we use to generate the
      U-Boot bootstream blob during image generation however Yocto image
      system enforces some naming schema so the symbolic links does work and
      we weren't following those. This patch uses the '${IMAGE_NAME}'
      variable and the proper image suffix so the symbolic links now fully
      work.
      
      Fixes [YOCTO #3871].
      
      Change-Id: I7f96dcdd58e0a726b8084c1f87ff10732fe259df
      Signed-off-by: default avatarOtavio Salvador <otavio@ossystems.com.br>
      c64d5870
  9. 21 Dec, 2012 1 commit
  10. 12 Dec, 2012 2 commits
  11. 04 Dec, 2012 1 commit
  12. 30 Oct, 2012 1 commit
  13. 29 Oct, 2012 1 commit
    • Andrei Gherzan's avatar
      image_types_fsl: Align SD partition and optimize final SD image · e6b33c90
      Andrei Gherzan authored
      SD image file was 4G in size but actually the rootfs partition was only
      60MB (in some images).
      The image file size is not fixed anymore but calculated inside this
      class. In this way we will setup the partition for rootfs to fit the
      ext file used as SDIMG_ROOTFS. By default the free space is calculated
      with IMAGE_OVERHEAD_FACTOR which is by default 1.3. If more free space
      is needed this can be overwritten.
      IMAGE_ROOTFS_ALIGNMENT set at 4096. This should be the best value for a
      SD card.
      Signed-off-by: default avatarAndrei Gherzan <andrei@gherzan.ro>
      e6b33c90
  14. 02 Oct, 2012 1 commit
  15. 24 Sep, 2012 1 commit
  16. 06 Aug, 2012 1 commit
  17. 17 Jul, 2012 2 commits
    • Otavio Salvador's avatar
      image_types_fsl.bbclass: do not create a partition from 0 to 1MB in i.MX sdcard · 053452d5
      Otavio Salvador authored
      The bootrom boots from a fixed 1K offset so we don't need a partition
      there and having one makes udev or kernel to probe for it and output
      error messages in bootlog:
      
      ,----[ boot error messages ]
      | ...
      | EXT4-fs (mmcblk0p1): VFS: Can't find ext4 filesystem
      | EXT3-fs (mmcblk0p1): error: can't find ext3 filesystem on dev mmcblk0p1.
      | EXT2-fs (mmcblk0p1): error: can't find an ext2 filesystem on dev mmcblk0p1.
      | FAT: bogus number of reserved sectors
      | VFS: Can't find a valid FAT filesystem on dev mmcblk0p1.
      | cramfs: wrong magic
      | FAT: bogus number of reserved sectors
      | VFS: Can't find a valid FAT filesystem on dev mmcblk0p1.
      | ...
      `----
      Signed-off-by: default avatarOtavio Salvador <otavio@ossystems.com.br>
      053452d5
    • Otavio Salvador's avatar
      image_types_fsl.bbclass: do not create a partition from 0 to 1MB in i.MX sdcard · a5716270
      Otavio Salvador authored
      The bootrom boots from a fixed 1K offset so we don't need a partition
      there and having one makes udev or kernel to probe for it and output
      error messages in bootlog:
      
      ,----[ boot error messages ]
      | ...
      | EXT4-fs (mmcblk0p1): VFS: Can't find ext4 filesystem
      | EXT3-fs (mmcblk0p1): error: can't find ext3 filesystem on dev mmcblk0p1.
      | EXT2-fs (mmcblk0p1): error: can't find an ext2 filesystem on dev mmcblk0p1.
      | FAT: bogus number of reserved sectors
      | VFS: Can't find a valid FAT filesystem on dev mmcblk0p1.
      | cramfs: wrong magic
      | FAT: bogus number of reserved sectors
      | VFS: Can't find a valid FAT filesystem on dev mmcblk0p1.
      | ...
      `----
      Signed-off-by: default avatarOtavio Salvador <otavio@ossystems.com.br>
      a5716270
  18. 10 Jul, 2012 1 commit
  19. 21 May, 2012 6 commits
  20. 18 May, 2012 3 commits
  21. 02 May, 2012 1 commit
  22. 01 May, 2012 1 commit
  23. 30 Apr, 2012 3 commits
  24. 29 Apr, 2012 1 commit
  25. 23 Mar, 2012 1 commit
  26. 22 Mar, 2012 1 commit
    • Otavio Salvador's avatar
      Major refactor in SDCard generation · 83534159
      Otavio Salvador authored
      The generation of SDCard has been completely refactored to work out of
      box; now to use it you have to set, e.g:
      
      SDCARD_ROOTFS = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.ext3"
      SDCARD_SIZE = "128"
      IMAGE_TYPES += "ext3 sdcard"
      
      Now the sdcard has following layout:
      
       0  - 1M                  - reserved to bootloader and other data
       1M - BOOT_SPACE          - kernel
       BOOT_SPACE - SDCARD_SIZE - rootfs
      
      All current supported machines on BSP will work out of box and
      generate a 2GB SDCard with an ext3 rootfs on it.
      Signed-off-by: default avatarOtavio Salvador <otavio@ossystems.com.br>
      83534159
  27. 21 Mar, 2012 1 commit
  28. 08 Mar, 2012 1 commit
    • Eric Bénard's avatar
      bbsdcard-image: add new class · 91a0d301
      Eric Bénard authored
      this class allows the generation of a ready to use SDCard image
      using barebox bootloader.
      
      example on how to use it (with angstrom distro) :
      1- add these 3 lines to your local.conf :
      ROOTFS = "${DEPLOY_DIR_IMAGE}/console-image-imx53qsb.ext3"
      INHERIT += "bbsdcard_image"
      BBSDIMG_SIZE = "512"
      
      2- build the image
      bitbake console-image
      
      3- copy it to the sdcard (update device for you sdcard, take care to not erase your hard drive ;-)
      sudo dd if=build/tmp-angstrom_2010_x-eglibc/deploy/images/imx53qsb/console-image-imx53qsb.bbsdimg of=/dev/mmcblk0
      Signed-off-by: default avatarEric Bénard <eric@eukrea.com>
      91a0d301
  29. 20 Dec, 2011 1 commit