devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "david@gibson.dropbear.id.au" <david@gibson.dropbear.id.au>
To: Anthony Ortega <anthony.ortega@terranorbital.com>
Cc: "devicetree-compiler@vger.kernel.org"
	<devicetree-compiler@vger.kernel.org>
Subject: Re: DTC Version and Reproducible Builds
Date: Fri, 20 Sep 2024 21:05:36 +1000	[thread overview]
Message-ID: <Zu1XAFqbtWnDcOmR@zatzit.fritz.box> (raw)
In-Reply-To: <PH1P110MB1507084A3C88BC2CBFAC984C8B63A@PH1P110MB1507.NAMP110.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 2683 bytes --]

On Thu, Sep 19, 2024 at 09:45:04PM +0000, Anthony Ortega wrote:
> David,
> 
> When I say DTC programs, I am referring to: convert-dtsv0, dtc,
> fdtdump, fdtget, fdtoverlay, fdtput

Ok.

> One other thing that wasn't immediately clear to me is if those
> tools are needed on the Linux side or just for U-Boot. In Buildroot
> it seems that U-Boot requires it when using Linux, which puts them
> in the Linux image. That could be another potential path forward.

I don't really understand the question.  They're userspace tools, so
whether you need them in any particular context depends on what you're
doing there.

> I'd be interested in seeing where the versioning logic was copied
> from. Since this seems to be the only package we are using that is
> doing this sort of versioning.

According to commit a657ce8f ("Add DTC release version information.")
it came from the Linux kernel... circa 2007.  The kernel's probably
doing something entirely different nowadays.

> Unfortunately, I don't think our system can be configured to use
> meson without a massive overhaul. In the short term I've applied a
> patch in our build that removes the line that grabs the commit tag
> during build.

That.. seems like a pretty serious limitation, given that more and
more packages are moving away from make.

But, in any case, I wasn't suggesting this as a practical workaround,
but more as a diagnostic.  If it works with meson we can look closer
at what it's doing and maybe duplicate it with make.

> 
> -Anthony
> 
> -----Original Message-----
> From: david@gibson.dropbear.id.au <david@gibson.dropbear.id.au>
> Sent: Tuesday, September 17, 2024 7:49 PM
> To: Anthony Ortega <anthony.ortega@terranorbital.com>
> Cc: devicetree-compiler@vger.kernel.org
> Subject: Re: DTC Version and Reproducible Builds
> 
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> 
> 
> This e-mail message and any attachments are intended solely for the specified addressee(s) and may be confidential, proprietary, privileged, and/or U.S. export controlled. If you are not the intended recipient, you are hereby notified that any use, disclosure, distribution, copying, or storage of this message or its attachments is strictly prohibited. Please immediately notify the sender by return e-mail and delete this message and any attachments.
> 

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-09-20 11:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PH1P110MB15070467257B855EE1B1BB008B60A@PH1P110MB1507.NAMP110.PROD.OUTLOOK.COM>
2024-09-18  2:48 ` DTC Version and Reproducible Builds david
2024-09-19 21:45   ` Anthony Ortega
2024-09-20 11:05     ` david [this message]
2024-09-23 10:46       ` Andreas Gnau
2024-09-24 11:10         ` david

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=Zu1XAFqbtWnDcOmR@zatzit.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=anthony.ortega@terranorbital.com \
    --cc=devicetree-compiler@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;
as well as URLs for NNTP newsgroup(s).