From: Simon Glass <sjg@chromium.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
Masahiro Yamada <masahiroy@kernel.org>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Nicolas Schier <nicolas@fjasle.eu>,
Tom Rini <trini@konsulko.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Nathan Chancellor <nathan@kernel.org>,
Nick Terrell <terrelln@fb.com>, Will Deacon <will@kernel.org>,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
Date: Tue, 5 Dec 2023 20:54:41 -0700 [thread overview]
Message-ID: <CAPnjgZ3QZh3+2PtmSvje=KAw1n1o_jmhgC1ZnhM9JBoEjLG+fQ@mail.gmail.com> (raw)
In-Reply-To: <92a3e3b4-6f4d-4ca4-947f-db905f328d4c@pengutronix.de>
Hi Ahmad,
On Tue, 5 Dec 2023 at 04:48, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>
> Hello Simon,
>
> On 02.12.23 04:54, Simon Glass wrote:
> > Add a script which produces a Flat Image Tree (FIT), a single file
> > containing the built kernel and associated devicetree files.
> > Compression defaults to gzip which gives a good balance of size and
> > performance.
> >
> > The files compress from about 86MB to 24MB using this approach.
> >
> > The FIT can be used by bootloaders which support it, such as U-Boot
> > and Linuxboot. It permits automatic selection of the correct
> > devicetree, matching the compatible string of the running board with
> > the closest compatible string in the FIT. There is no need for
> > filenames or other workarounds.
> >
> > Add a 'make image.fit' build target for arm64, as well. Use
> > FIT_COMPRESSION to select a different algorithm.
> >
> > The FIT can be examined using 'dumpimage -l'.
> >
> > This features requires pylibfdt (use 'pip install libfdt'). It also
> > requires compression utilities for the algorithm being used. Supported
> > compression options are the same as the Image.xxx files. For now there
> > is no way to change the compression other than by editing the rule for
> > $(obj)/image.fit
> >
> > While FIT supports a ramdisk / initrd, no attempt is made to support
> > this here, since it must be built separately from the Linux build.
> >
> > Signed-off-by: Simon Glass <sjg@chromium.org>
>
> kernel_noload support is now in barebox next branch and I tested this
> series against it:
>
> Tested-by: Ahmad Fatoum <a.fatoum@pengutronix.de> # barebox
>
OK great thank you.
> > +"""Build a FIT containing a lot of devicetree files
> > +
> > +Usage:
> > + make_fit.py -A arm64 -n 'Linux-6.6' -O linux
> > + -f arch/arm64/boot/image.fit -k /tmp/kern/arch/arm64/boot/image.itk
> > + /tmp/kern/arch/arm64/boot/dts/ -E -c gzip
> > +
> > +Creates a FIT containing the supplied kernel and a directory containing the
> > +devicetree files.
> > +
> > +Use -E to generate an external FIT (where the data is placed after the
> > +FIT data structure). This allows parsing of the data without loading
> > +the entire FIT.
> > +
> > +Use -c to compress the data, using bzip2, gzip, lz4, lzma, lzo and
> > +zstd algorithms.
> > +
> > +The resulting FIT can be booted by bootloaders which support FIT, such
> > +as U-Boot, Linuxboot, Tianocore, etc.
>
> Feel free to add barebox to the list. Did you check whether Linuxboot and
> Tianocore support kernel_noload?
Only what I was told by people in those projects. They may not even
look at the load address, but I am not an expert on that.
>
> > + fsw.property_u32('load', 0)
> > + fsw.property_u32('entry', 0)
>
> I still think load and entry dummy values are confusing and should be dropped.
This is what the spec requires at present. But I agree we should
change it. I will dig into that at some point to see what is needed.
>
> > + with fsw.add_node(f'fdt-{seq}'):
> > + # Get the compatible / model information
> > + with open(fname, 'rb') as inf:
> > + data = inf.read()
> > + fdt = libfdt.FdtRo(data)
> > + model = fdt.getprop(0, 'model').as_str()
> > + compat = fdt.getprop(0, 'compatible')
> > +
> > + fsw.property_string('description', model)
> > + fsw.property_string('type', 'flat_dt')
> > + fsw.property_string('arch', arch)
> > + fsw.property_string('compression', compress)
> > + fsw.property('compatible', bytes(compat))
> > +
> > + with open(fname, 'rb') as inf:
> > + compressed = compress_data(inf, compress)
> > + fsw.property('data', compressed)
> > + return model, compat
>
> After Doug's elaboration, extracting multiple compatibles is fine by me.
OK good.
Regards,
Simon
next prev parent reply other threads:[~2023-12-06 3:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 3:54 [PATCH v9 0/2] arm64: Add a build target for " Simon Glass
2023-12-02 3:54 ` [PATCH v9 2/2] arm64: boot: Support " Simon Glass
2023-12-03 15:34 ` Laurent Pinchart
2023-12-04 17:59 ` Simon Glass
2023-12-07 14:27 ` Chen-Yu Tsai
2023-12-07 14:38 ` Laurent Pinchart
2023-12-07 20:52 ` Simon Glass
2023-12-07 21:30 ` Laurent Pinchart
2023-12-09 13:13 ` Chen-Yu Tsai
2023-12-09 15:29 ` Laurent Pinchart
2023-12-09 16:31 ` Geert Uytterhoeven
2023-12-14 4:02 ` Chen-Yu Tsai
2023-12-14 6:12 ` Masahiro Yamada
2023-12-14 7:33 ` Masahiro Yamada
2023-12-29 6:38 ` Simon Glass
2024-01-02 3:19 ` Chen-Yu Tsai
2024-01-09 13:47 ` Masahiro Yamada
2024-01-10 3:47 ` Chen-Yu Tsai
2024-01-02 15:53 ` Ahmad Fatoum
2024-01-09 14:33 ` Rasmus Villemoes
2023-12-14 7:57 ` Geert Uytterhoeven
2023-12-14 12:48 ` Tom Rini
2023-12-05 11:48 ` Ahmad Fatoum
2023-12-06 3:54 ` Simon Glass [this message]
2023-12-08 11:49 ` Nicolas Schier
2023-12-13 12:13 ` Will Deacon
2024-01-02 23:46 ` Simon Glass
2024-01-09 14:01 ` Masahiro Yamada
2024-01-09 14:33 ` Tom Rini
2024-01-17 13:14 ` Simon Glass
2024-01-25 16:03 ` Simon Glass
2024-01-30 9:16 ` Masahiro Yamada
2024-01-31 22:02 ` Rob Herring
2024-02-01 2:08 ` Masahiro Yamada
2024-02-01 21:03 ` Rob Herring
2024-02-02 5:37 ` Masahiro Yamada
2024-02-02 16:00 ` Simon Glass
2024-02-02 16:00 ` Simon Glass
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='CAPnjgZ3QZh3+2PtmSvje=KAw1n1o_jmhgC1ZnhM9JBoEjLG+fQ@mail.gmail.com' \
--to=sjg@chromium.org \
--cc=a.fatoum@pengutronix.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=terrelln@fb.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=will@kernel.org \
--cc=workflows@vger.kernel.org \
/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