public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mathew McBride <matt@bionicmessage.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] SquashFS and FIT images
Date: Fri, 26 Jan 2018 10:09:37 +1100	[thread overview]
Message-ID: <p4dnvj$b5q$1@blaine.gmane.org> (raw)
In-Reply-To: <7f8bf7de8bae40288fe0a5c5b9344bc8@ERDCSEXCH01.SMITHSSII.NET>

On 26/01/2018 8:01 AM, Bishop, Mark (STRT) wrote:
> Is it possible to specify squashFS images in an .its file?  If so, anyone have an example or a pointer to the docs I've been searching for?
> Hi Mark,
It is possible, here is an example I have used on an NXP LS1043 board:
/dts-v1/;

/ {
         description = "ARM64 OpenWrt FIT (Flattened Image Tree)";
         #address-cells = <1>;

         images {
                 kernel at 1 {
                         description = "ARM64 OpenWrt Linux-4.4";
                         data = /incbin/("arch/arm64/boot/Image.gz");
                         type = "kernel";
                         arch = "arm64";
                         os = "linux";
                         compression = "gzip";
                         load = <0x80080000>;
                         entry = <0x80080000>;
                 };


                 ramdisk at 1 {
                         description = "ARM64 OpenWrt ramdisk";
                         data = /incbin/("root.squashfs");
                         type = "ramdisk";
                         arch = "arm64";
                         os = "linux";
                         compression = "gzip";
                 };


                 fdt at 1 {
                         description = "ARM64 OpenWrt device tree blob";
                         data = 
/incbin/("arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb.dtb");
                         type = "flat_dt";
                         arch = "arm64";
                         compression = "none";
                         load = <0x90000000>;
                 };


         };

         configurations {
                 default = "config at 1";
                 config at 1 {
                         description = "OpenWrt";
                         kernel = "kernel at 1";
                         fdt = "fdt at 1";
                         ramdisk = "ramdisk at 1";
                 };
         };
};

Cheers,
Matt

> Mark Bishop
> Sr. Firmware/Software Engineer - Microwave Subsystems
> 
> [cid:image001.png at 01D281ED.A45F0A90]
> 
> 4726 Eisenhower Blvd.
> Tampa, FL 33634
> USA
> 
> 
> T  +1 813 901 7293
> 
> mbishop at smithsinterconnectinc.com<mailto:mbishop@smithsinterconnectinc.com>
> 
> smithsinterconnect.com<http://www.smithsinterconnect.com/>
> 
> TRAK MICROWAVE IS NOW SMITHS INTERCONNECT!
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
> 

  reply	other threads:[~2018-01-25 23:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 21:01 [U-Boot] SquashFS and FIT images Bishop, Mark
2018-01-25 23:09 ` Mathew McBride [this message]
     [not found]   ` <CAFOYHZDwV826hm+z_k5jaMyDph_LkAQYcd8YwYH3ZFBe+ChDmw@mail.gmail.com>
     [not found]     ` <CAFOYHZDZ0GfoQbAcC8yfKyqm2d2Yj7=OYNL3Nv7NMPhKpQDaEQ@mail.gmail.com>
2018-01-26  2:25       ` Chris Packham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='p4dnvj$b5q$1@blaine.gmane.org' \
    --to=matt@bionicmessage.net \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox