From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Justin Covell <jujugoboom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Devicetree Compiler
<devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/1] libfdt: Change last_comp_version to fit spec
Date: Wed, 2 Dec 2020 08:25:04 -0700 [thread overview]
Message-ID: <CAL_Jsq+aio50a18QrwA6VbxZmOYyzcC+tRkkxPkBPyLNcfh-5w@mail.gmail.com> (raw)
In-Reply-To: <20201202074627.GA87-cyTpl0DnfLBQ0J4zD59KJAH0AcctZ4a01BehtkLrGTY@public.gmane.org>
On Wed, Dec 2, 2020 at 12:46 AM Justin Covell <jujugoboom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> On Mon, Nov 30, 2020 at 10:22:09AM -0700, Rob Herring wrote:
> > On Tue, Nov 24, 2020 at 10:50 AM Justin Covell <jujugoboom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > >
> >
> > Needs a commit message. For a single patch, you don't need a cover
> > letter. The explanation should be here.
> >
> > Besides matching the spec, what problem are you trying to solve?
> >
>
> Sorry about that, first time contributing. I'm trying to help with
> interoperability with other libraries that are made to read/write DTBs
> by matching the spec.
What library? Why does libfdt not work?
> > > ---
> > > libfdt/fdt_sw.c | 2 +-
> > > libfdt/libfdt.h | 1 +
> > > 2 files changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/libfdt/fdt_sw.c b/libfdt/fdt_sw.c
> > > index 68b543c..4c569ee 100644
> > > --- a/libfdt/fdt_sw.c
> > > +++ b/libfdt/fdt_sw.c
> > > @@ -377,7 +377,7 @@ int fdt_finish(void *fdt)
> > > fdt_set_totalsize(fdt, newstroffset + fdt_size_dt_strings(fdt));
> > >
> > > /* And fix up fields that were keeping intermediate state. */
> > > - fdt_set_last_comp_version(fdt, FDT_FIRST_SUPPORTED_VERSION);
> > > + fdt_set_last_comp_version(fdt, FDT_LAST_COMPATIBLE_VERSION);
> > > fdt_set_magic(fdt, FDT_MAGIC);
> > >
> > > return 0;
> > > diff --git a/libfdt/libfdt.h b/libfdt/libfdt.h
> > > index 89adee3..abad93b 100644
> > > --- a/libfdt/libfdt.h
> > > +++ b/libfdt/libfdt.h
> > > @@ -14,6 +14,7 @@ extern "C" {
> > > #endif
> > >
> > > #define FDT_FIRST_SUPPORTED_VERSION 0x02
> > > +#define FDT_LAST_COMPATIBLE_VERSION 0x10
> >
> > If the above change is correct (I'm not sure it is offhand), why not
> > just bump up FDT_FIRST_SUPPORTED_VERSION value?
> >
>
> I didn't want to bump the FDT_FIRST_SUPPORTED_VERSION to maintin
> backwards compatability, and assumed that libfdt actually does support
> working with DTBs down to version 2.
Looking at this more closely, I think your change is correct. It's
actually fixing a regression. Prior to commit f1879e1a50eb ("Add
limited read-only support for older (V2 and V3) device tree to
libfdt."), libfdt would set last_comp_version to 16. Now it sets it to
2, but really 2 is what libfdt can read, not what should be in
last_comp_version.
Also, I'm not certain what happens if you tried to modify a version 2
dtb. It doesn't look like we do anything to fail gracefully.
Rob
next prev parent reply other threads:[~2020-12-02 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 17:49 [PATCH 0/1] libfdt: Change last_comp_version to fit spec Justin Covell
[not found] ` <20201124174945.5399-1-jujugoboom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-11-24 17:49 ` [PATCH 1/1] " Justin Covell
[not found] ` <20201124174945.5399-2-jujugoboom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-11-30 17:22 ` Rob Herring
[not found] ` <CAL_Jsq+CZA8weCYPcJYOdY3-z8fnwibsKhfGwO8nuy+7RH=pvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-12-02 7:46 ` Justin Covell
[not found] ` <20201202074627.GA87-cyTpl0DnfLBQ0J4zD59KJAH0AcctZ4a01BehtkLrGTY@public.gmane.org>
2020-12-02 15:25 ` Rob Herring [this message]
[not found] ` <CAL_Jsq+aio50a18QrwA6VbxZmOYyzcC+tRkkxPkBPyLNcfh-5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-12-03 1:21 ` Justin Covell
[not found] ` <20201203012147.GA87-cyTpl0DnfLBQ0J4zD59KJAH0AcctZ4a01BehtkLrGTY@public.gmane.org>
2020-12-03 6:16 ` David Gibson
2020-12-03 6:12 ` David Gibson
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=CAL_Jsq+aio50a18QrwA6VbxZmOYyzcC+tRkkxPkBPyLNcfh-5w@mail.gmail.com \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jujugoboom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).