From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Andrejs Cainikovs <andrejs.cainikovs@toradex.com>,
Brandon Maier <brandon.maier@collins.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH v3 2/3] buildman: Allow skipping the dtc build
Date: Fri, 16 Aug 2024 11:22:37 -0600 [thread overview]
Message-ID: <20240816172237.GA1626301@bill-the-cat> (raw)
In-Reply-To: <20240815195746.749042-3-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Thu, Aug 15, 2024 at 01:57:45PM -0600, Simon Glass wrote:
> For most boards, the device-tree compiler is built in-tree, ignoring the
> system version. Add a special option to skip this build. This can be
> useful when the system dtc is up-to-date, as it speeds up the build.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> (no changes since v1)
>
> tools/buildman/builder.py | 27 ++++++++++++++++++++++++++-
> tools/buildman/builderthread.py | 4 ++--
> tools/buildman/buildman.rst | 3 +++
> tools/buildman/cmdline.py | 2 ++
> tools/buildman/control.py | 3 ++-
> tools/buildman/test.py | 31 +++++++++++++++++++++++++++++++
> 6 files changed, 66 insertions(+), 4 deletions(-)
We should probably do this more generically, outside of buildman. We
have scripts/dtc-version.sh and if the system version isn't new enough
(and we just need to define whatever the minimum version is), then we
build our (not currently that new anymore) dtc instead.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-08-16 17:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 19:57 [PATCH v3 0/3] This series adds a few patches to make it easy to use the system dtc in Simon Glass
2024-08-15 19:57 ` [PATCH v3 1/3] buildman: Support building within a Python venv Simon Glass
2024-09-06 0:53 ` Simon Glass
2024-08-15 19:57 ` [PATCH v3 2/3] buildman: Allow skipping the dtc build Simon Glass
2024-08-16 17:22 ` Tom Rini [this message]
2024-08-16 23:53 ` Simon Glass
2024-08-22 3:00 ` Simon Glass
2024-08-22 14:10 ` Tom Rini
2024-08-22 14:15 ` Simon Glass
2024-09-01 20:09 ` Simon Glass
2024-09-02 15:39 ` Tom Rini
2024-09-10 18:41 ` Simon Glass
2024-09-10 18:42 ` Tom Rini
2024-09-10 18:45 ` Simon Glass
2024-09-10 18:52 ` Tom Rini
2024-09-10 20:14 ` Simon Glass
2024-09-10 22:07 ` Tom Rini
2024-09-12 1:01 ` Simon Glass
2024-09-12 17:44 ` Tom Rini
2024-09-19 14:13 ` Simon Glass
2024-09-26 22:07 ` Simon Glass
2024-08-15 19:57 ` [PATCH v3 3/3] RFC: CI: Skip building dtc for world builds Simon Glass
2024-10-10 18:50 ` Simon Glass
2024-10-10 19:01 ` Tom Rini
2024-10-14 19:13 ` Simon Glass
2024-10-14 22:43 ` Tom Rini
2024-09-06 22:37 ` (subset) [PATCH v3 0/3] This series adds a few patches to make it easy to use the system dtc in Tom Rini
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=20240816172237.GA1626301@bill-the-cat \
--to=trini@konsulko.com \
--cc=andrejs.cainikovs@toradex.com \
--cc=brandon.maier@collins.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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