08 Dec, 2009

15 commits


06 Dec, 2009

1 commit


05 Dec, 2009

6 commits

  • The Linux kernel build system changed how it compresses things with LZMA
    such that the header no longer contains the filesize (it is instead set to
    all F's). So if we get a LZMA image that has -1 for the 64bit field,
    let's just assume that the decompressed size is unknown and continue on.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     
  • Two later additions to the Configuration Option section unfortunately
    split the description of Show boot progress and the list of its call outs.

    Signed-off-by: Detlev Zundel

    Detlev Zundel
     
  • Previously, there was no indication to the user that a FIT image was
    successfully created after executing mkimage. For example:

    $ mkimage -f uImage.its uImage.itb
    DTC: dts->dtb on file "uImage.its"

    Adding some additional output after creating a FIT image lets the user
    know exactly what is contained in their image, eg:

    $ mkimage -f uImage.its uImage.itb
    DTC: dts->dtb on file "uImage.its"
    FIT description: Linux kernel 2.6.32-rc7-00201-g7550d6f-dirty
    Created: Tue Nov 24 15:43:01 2009
    Image 0 (kernel@1)
    Description: Linux Kernel 2.6.32-rc7-00201-g7550d6f-dirty
    Type: Kernel Image
    Compression: gzip compressed
    Data Size: 2707311 Bytes = 2643.86 kB = 2.58 MB
    Architecture: PowerPC
    OS: Linux
    Load Address: 0x00000000
    Entry Point: 0x00000000
    Hash algo: crc32
    Hash value: efe0798b
    Hash algo: sha1
    Hash value: ecafba8c95684f2c8fec67e33c41ec88df1534d7
    Image 1 (fdt@1)
    Description: Flattened Device Tree blob
    Type: Flat Device Tree
    Compression: uncompressed
    Data Size: 12288 Bytes = 12.00 kB = 0.01 MB
    Architecture: PowerPC
    Hash algo: crc32
    Hash value: a5cab676
    Hash algo: sha1
    Hash value: 168722b13e305283cfd6603dfe8248cc329adea6
    Default Configuration: 'config@1'
    Configuration 0 (config@1)
    Description: Default Linux kernel
    Kernel: kernel@1
    FDT: fdt@1

    This brings the behavior of creating a FIT image in line with creating a
    standard uImage, which also prints out the uImage contents after
    creation.

    Signed-off-by: Peter Tyser

    Peter Tyser
     
  • The FIT fit_set_header() function was copied from the standard uImage's
    image_set_header() function during mkimage reorganization. However, the
    fit_set_header() function is not used since FIT images use a standard
    device tree blob header.

    Signed-off-by: Peter Tyser

    Peter Tyser
     
  • When building a Flattened Image Tree (FIT) the image type needs to be
    "flat_dt". Commit 89a4d6b12fd6394898b8a454cbabeaf1cd59bae5 introduced a
    regression which caused the user to need to specify the "-T flat_dt"
    parameter on the command line when building a FIT image. The "-T
    flat_dt" parameter should not be needed and is at odds with the current
    FIT image documentation.

    Signed-off-by: Peter Tyser

    Peter Tyser
     
  • extfs.c assumes that there is always a valid inode_size field in the
    superblock. But this is not true for ext2fs rev 0. Such ext2fs images
    are for instance generated by genext2fs. Symptoms on ARM machines are
    messages like: "raise: Signal # 8 caught"; on PowerPC "ext2ls" will
    print nothing.
    This fix checks for rev 0 and uses then 128 bytes as inode size.

    Signed-off-by: Michael Brandt
    Tested on: TQM5200S
    Tested-by: Wolfgang Denk
    Signed-off-by: Wolfgang Denk

    Michael Brandt
     

03 Dec, 2009

13 commits


01 Dec, 2009

1 commit


25 Nov, 2009

4 commits