20 Oct, 2015

1 commit


06 Jun, 2015

1 commit

  • This fixes the following compiler warning:

    In file included from tools/common/image-fit.c:1:0:
    ./tools/../common/image-fit.c: In function ‘fit_conf_print’:
    ./tools/../common/image-fit.c:1470:27: warning: logical not is only applied
    to the left hand side of comparison [-Wlogical-not-parentheses]
    (const char **)&uname) > 0;

    Signed-off-by: Hans de Goede

    Hans de Goede
     

28 May, 2015

2 commits

  • Added a trimmed down instance of boot_get_() to satisfy the
    minimum requierments of the added feature. The function follows the
    normal patterns set by other boot_get's, which should make it a
    bit easier to combine them all together into one boot_get_image()
    function in a later refactor.

    Documentation for the new function can be found in source:
    include/image.h

    Signed-off-by: Karl Apsite
    Reviewed-by: Simon Glass

    Karl Apsite
     
  • Added FIT_LOADABLE_PROP, so the user can identify an optional entry
    named "loadables" in their .its configuration. "loadables" is a comma
    separated list in the .its

    Documentation can be found in doc/uImage.FIT/source_file_format.txt and
    doc/uImage.Fit/multi-with-loadables.its

    Signed-off-by: Karl Apsite
    Reviewed-by: Simon Glass

    Karl Apsite
     

19 Apr, 2015

1 commit


17 Feb, 2015

1 commit


30 Jan, 2015

1 commit

  • The dumpimage is able to extract components contained in a FIT image:

    $ ./dumpimage -T flat_dt -i CONTAINER.ITB -p INDEX FILE

    The CONTAINER.ITB is a regular FIT container file. The INDEX is the poisition
    of the sub-image to be retrieved, and FILE is the file (path+name) to save the
    extracted sub-image.

    For example, given the following kernel.its to build a kernel.itb:

    /dts-v1/;
    / {
    ...
    images {
    kernel@1 {
    description = "Kernel 2.6.32-34";
    data = /incbin/("/boot/vmlinuz-2.6.32-34-generic");
    type = "kernel";
    arch = "ppc";
    os = "linux";
    compression = "gzip";
    load = ;
    entry = ;
    hash@1 {
    algo = "md5";
    };
    };
    ...
    };
    ...
    };

    The dumpimage can extract the 'kernel@1' node through the following command:

    $ ./dumpimage -T flat_dt -i kernel.itb -p 0 kernel
    Extracted:
    Image 0 (kernel@1)
    Description: Kernel 2.6.32-34
    Created: Wed Oct 22 15:50:26 2014
    Type: Kernel Image
    Compression: gzip compressed
    Data Size: 4040128 Bytes = 3945.44 kB = 3.85 MB
    Architecture: PowerPC
    OS: Linux
    Load Address: 0x00000000
    Entry Point: 0x00000000
    Hash algo: md5
    Hash value: 22352ad39bdc03e2e50f9cc28c1c3652

    Which results in the file 'kernel' being exactly the same as '/boot/vmlinuz-2.6.32-34-generic'.

    Signed-off-by: Guilherme Maciel Ferreira

    Guilherme Maciel Ferreira
     

15 Jan, 2015

1 commit


29 Oct, 2014

1 commit


25 Oct, 2014

1 commit


22 Oct, 2014

2 commits


29 Aug, 2014

1 commit

  • Commit e3a5bbce broke the FIT image tests by not loading a ramdisk even if
    a load address is provided in the FIT. The rationale was that a load address
    of 0 should be considered to mean 'do not load'.

    Add a new load operation which supports this feature, so that the ramdisk
    will be loaded if a non-zero load address is provided.

    Signed-off-by: Simon Glass

    Simon Glass
     

19 Jun, 2014

5 commits


12 Jun, 2014

1 commit


22 Mar, 2014

1 commit


20 Feb, 2014

1 commit


20 Sep, 2013

3 commits


17 Aug, 2013

1 commit

  • The timestamp is shown in fit_print_contents() but for some reason not
    in fit_image_print(). This seems to be an oversight, since it is the latter
    which is used by bootm.

    Add timestamp printing in this case.

    (There is code duplication in these two function, for looking at in a future
    patch).

    Signed-off-by: Simon Glass

    Simon Glass
     

24 Jul, 2013

1 commit


12 Jul, 2013

1 commit

  • If a specific configuraion is selected by the bootm command, e.g. with
    'bootm 84000000#recoveryconf' we must honour this for not just the kernel,
    but also the ramdisk and FDT.

    In the conversion to using a common fit_image_load() function for loading
    images from FITs (commits a51ec63 and 53f375f) this feature was lost.
    Reinstate it by passing the selected configuration back from
    fit_image_load() to boot_get_kernel(), then use this configuration
    (which is stored in images->fit_uname_cfg) in both boot_get_ramdisk()
    and boot_get_fdt().

    Signed-off-by: Simon Glass

    Simon Glass
     

26 Jun, 2013

1 commit

  • Add support for signing images using a new signature node. The process
    is handled by fdt_add_verification_data() which now takes parameters to
    provide the keys and related information.

    Signed-off-by: Simon Glass

    Simon Glass
     

17 Jun, 2013

1 commit


05 Jun, 2013

5 commits


15 May, 2013

6 commits