From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Rob Herring <robh@kernel.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 2/6] kbuild: add dtc as dependency on .dtb files
Date: Thu, 1 Mar 2018 14:45:49 +0900 [thread overview]
Message-ID: <CAK7LNAT+_0t4PQxW911a0xL-f54WHGbF8t3rEq2Pfngr3J7BOQ@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNAQSJ1uzgmta76rJwDpi08SB5gwcRPxu_TPw0u0XzgGaJA@mail.gmail.com>
2018-03-01 13:33 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.com>:
> 2018-03-01 8:32 GMT+09:00 Rob Herring <robh@kernel.org>:
>> If dtc is rebuilt, we should rebuild .dtb files with the new dtc.
>>
>> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
>> Signed-off-by: Rob Herring <robh@kernel.org>
>
>
> Hmm, I am not 100% sure about this.
>
> Is there a case where resulted DTBs
> depend on DTC version?
>
>
> If I understand correctly,
> DTS and DTB are 1:1
> Unlike CC, there is no room for optimization.
Maybe I was wrong.
Is there room for optimization
in 'DT strings' section?
I guess it is optimized enough to avoid string duplication,
but there could be different results
without changing the specification.
> Some possibilities could be:
> - specification is updated.
> ( /dts-v1/ in DTS should be updated if so)
> - buggy DTC version generates broken DTBs.
>
>
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2018-03-01 5:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 23:32 [PATCH 0/6] dtc updates for 4.17 Rob Herring
2018-02-28 23:32 ` [PATCH 1/6] kbuild: remove remaining use of undefined YACC_PREFIX Rob Herring
2018-03-01 4:20 ` Masahiro Yamada
2018-03-01 11:35 ` Masahiro Yamada
2018-03-01 13:39 ` Rob Herring
2018-03-01 14:01 ` Masahiro Yamada
2018-03-01 15:38 ` Rob Herring
2018-02-28 23:32 ` [PATCH 2/6] kbuild: add dtc as dependency on .dtb files Rob Herring
2018-03-01 4:33 ` Masahiro Yamada
2018-03-01 5:45 ` Masahiro Yamada [this message]
2018-03-01 13:28 ` Rob Herring
2018-03-01 14:04 ` Masahiro Yamada
2018-02-28 23:32 ` [PATCH 3/6] scripts: re-enable some now fixed dtc warnings Rob Herring
2018-02-28 23:32 ` [PATCH 4/6] scripts/dtc: generate lexer and parser during build instead of shipping Rob Herring
2018-03-01 4:34 ` Masahiro Yamada
2018-03-01 18:13 ` Rob Herring
2018-02-28 23:32 ` [PATCH 5/6] scripts/dtc: Update to upstream version v1.4.6-9-gaadd0b65c987 Rob Herring
2018-02-28 23:32 ` [PATCH 6/6] scripts: turn off some new dtc warnings by default Rob Herring
2018-03-01 4:43 ` [PATCH 0/6] dtc updates for 4.17 Masahiro Yamada
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=CAK7LNAT+_0t4PQxW911a0xL-f54WHGbF8t3rEq2Pfngr3J7BOQ@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).