From: Herve Codina <herve.codina@bootlin.com>
To: David Gibson <david@gibson.dropbear.id.au>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Ayush Singh <ayush@beagleboard.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
devicetree-compiler@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree-spec@vger.kernel.org,
Hui Pu <hui.pu@gehealthcare.com>,
Ian Ray <ian.ray@gehealthcare.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [RFC PATCH 00/15] Add support for structured tags and v18 dtb version
Date: Thu, 12 Mar 2026 08:54:00 +0100 [thread overview]
Message-ID: <20260312085400.3a11df8b@bootlin.com> (raw)
In-Reply-To: <20260210173349.636766-1-herve.codina@bootlin.com>
Hi David,
On Tue, 10 Feb 2026 18:33:28 +0100
Herve Codina <herve.codina@bootlin.com> wrote:
> Recently, I sent a RFC series related to support for metadata and addon
> device-trees [1].
>
> During the discussion the concept of structured tags and "unknown" tags
> emerged as well as the need to have them handled as a prerequisite of
> support for metadata and addon.
>
> The conclusion was the need for a new dtb version (v18) with support
> for:
> - Structured tags and based on them, "unknown" tags.
> Those structured tags allow to have an standardized definition of
> tags with the capability of skipping a tag and its related data
> when a "unknown" tag is incountered by a given version of libfdt,
> dtc and tools. Those "unknown" tags are tags defined in future
> versions. Even if they exact meaning is unknown for an 'old'
> version, they structure is understood and the 'old' version can skip
> them without any errors if allowed.
>
> - Flags in the dtb header (dt_flags).
> The goal of this field is to have a placeholder to specify the
> type of dtb we are dealing with. For instance, addons dtb will set a
> flag in this placeholder
>
> - A last compatible version for writing purpose.
> The goal of the new dtb header field (last_comp_version_w) is to
> disable globally any modification. It works similarly to
> last_comp_version but for modification. It can be used to avoid any
> modification that could be done by an 'old' version and could lead
> to inconsistencies between the modification itself and some
> "unknown" tags.
>
> This RFC series implements those features and leads to the v18 dtb
> version.
I sent this series a month ago.
I know some patches have been applied but what's the plan for the remaining
ones?
Is there anything I can do to help move things forward?
Let me know if you want some rebase and/or modification and so a new version
of the series or if you need anything else that can help in moving forward.
Best regards,
Hervé
next prev parent reply other threads:[~2026-03-12 7:54 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 17:33 [RFC PATCH 00/15] Add support for structured tags and v18 dtb version Herve Codina
2026-02-10 17:33 ` [RFC PATCH 01/15] dtc: Use a consistent type for basenamelen Herve Codina
2026-02-13 6:14 ` David Gibson
2026-02-10 17:33 ` [RFC PATCH 02/15] fdtdump: Remove dtb version check Herve Codina
2026-02-14 2:12 ` David Gibson
2026-02-10 17:33 ` [RFC PATCH 03/15] fdtdump: Return an error code on wrong tag value Herve Codina
2026-02-23 5:38 ` David Gibson
2026-02-23 8:39 ` Herve Codina
2026-02-24 5:57 ` David Gibson
2026-02-10 17:33 ` [RFC PATCH 04/15] libfdt: fdt_rw: Introduce fdt_downgrade_version() Herve Codina
2026-02-24 6:09 ` David Gibson
2026-02-10 17:33 ` [RFC PATCH 05/15] libfdt: Introduce fdt_first_node() Herve Codina
2026-04-01 15:11 ` Luca Ceresoli
2026-04-03 7:07 ` Herve Codina
2026-02-10 17:33 ` [RFC PATCH 06/15] libfdt: Don't assume that a FDT_BEGIN_NODE tag is available at offset 0 Herve Codina
2026-04-01 15:11 ` Luca Ceresoli
2026-04-07 8:51 ` Herve Codina
2026-02-10 17:33 ` [RFC PATCH 07/15] libfdt: fdt_check_full: Handle FDT_NOP when FDT_END is expected Herve Codina
2026-03-04 10:08 ` David Gibson
2026-02-10 17:33 ` [RFC PATCH 08/15] tests: asm: Introduce treehdr_vers macro Herve Codina
2026-02-10 17:33 ` [RFC PATCH 09/15] Introduce structured tag value definition Herve Codina
2026-04-01 15:11 ` Luca Ceresoli
2026-04-07 11:42 ` Herve Codina
2026-02-10 17:33 ` [RFC PATCH 10/15] fdtdump: Handle unknown tags Herve Codina
2026-04-01 15:15 ` Luca Ceresoli
2026-04-07 14:03 ` Herve Codina
2026-04-07 15:46 ` Luca Ceresoli
2026-02-10 17:33 ` [RFC PATCH 11/15] flattree: " Herve Codina
2026-04-01 15:15 ` Luca Ceresoli
2026-02-10 17:33 ` [RFC PATCH 12/15] libfdt: Handle unknown tags in fdt_get_next() Herve Codina
2026-04-01 15:17 ` Luca Ceresoli
2026-04-07 14:29 ` Herve Codina
2026-02-10 17:33 ` [RFC PATCH 13/15] libfdt: Introduce fdt_ptr_offset_ Herve Codina
2026-04-01 15:18 ` Luca Ceresoli
2026-02-10 17:33 ` [RFC PATCH 14/15] libfdt: Handle unknown tags on dtb modifications Herve Codina
2026-04-01 15:18 ` Luca Ceresoli
2026-04-07 15:41 ` Herve Codina
2026-02-10 17:33 ` [RFC PATCH 15/15] Introduce v18 dtb version Herve Codina
2026-04-01 15:19 ` Luca Ceresoli
2026-04-07 16:44 ` Herve Codina
2026-04-08 7:55 ` Luca Ceresoli
2026-03-12 7:54 ` Herve Codina [this message]
2026-03-12 10:21 ` [RFC PATCH 00/15] Add support for structured tags and " David Gibson
2026-03-16 16:16 ` Herve Codina
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=20260312085400.3a11df8b@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=ayush@beagleboard.org \
--cc=conor+dt@kernel.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=hui.pu@gehealthcare.com \
--cc=ian.ray@gehealthcare.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.