public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: u-boot@lists.denx.de
Subject: Reproducibility regression with mx6cuboxi
Date: Tue, 21 Jul 2020 15:54:19 -0700	[thread overview]
Message-ID: <87k0yw7a3o.fsf@ponder> (raw)
In-Reply-To: <20200721222421.GG6227@bill-the-cat>

On 2020-07-21, Tom Rini wrote:
> On Sun, Jul 19, 2020 at 11:23:05AM -0700, Vagrant Cascadian wrote:
>
>> The mx6cuboxi target no longer builds reproducibility on Debian. I've
>> bisected it down to:
>> 
>>   eb9124f5748c96ffd548e50fd6989c3b5395b353 mx6cuboxi: enable OF_CONTROL with DM_MMC and DM_USB
>
> Are you tracking any other platforms which use OF_CONTROL?  Thanks!

Several in the imx family, all of which appear to be building
reproducibly:

$ zgrep CONFIG_OF_CONTROL=y usr/share/doc/u-boot-imx/configs/config.*
usr/share/doc/u-boot-imx/configs/config.dh_imx6.gz:CONFIG_OF_CONTROL=y
usr/share/doc/u-boot-imx/configs/config.mx6cuboxi.gz:CONFIG_OF_CONTROL=y
usr/share/doc/u-boot-imx/configs/config.mx6qsabrelite.gz:CONFIG_OF_CONTROL=y
usr/share/doc/u-boot-imx/configs/config.nitrogen6q.gz:CONFIG_OF_CONTROL=y
usr/share/doc/u-boot-imx/configs/config.novena-rawsd.gz:CONFIG_OF_CONTROL=y
usr/share/doc/u-boot-imx/configs/config.novena.gz:CONFIG_OF_CONTROL=y
usr/share/doc/u-boot-imx/configs/config.wandboard.gz:CONFIG_OF_CONTROL=y

dh_imx6 did have reproducibility issues around u-boot 2020.04, but
haven't seen them in 2020.07-rc1 or newer, so I haven't bothered to
bisect or look into it further.

CONFIG_OF_CONTROL is enabled in many other boards in the Debian packages
without issue.

The dra7xx_evm platform has reproducibility issues introduced
approximately the same time, but I haven't been able to trigger the
issue in my local test environment (which is a little less comprehensive
than what tests.reproducible-builds.org does). I'll try to do some more
testing of that one soon, but that should probably be it's own thread as
it seems unrelated.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200721/59b2b26d/attachment.sig>

  reply	other threads:[~2020-07-21 22:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19 18:23 Reproducibility regression with mx6cuboxi Vagrant Cascadian
2020-07-21 22:24 ` Tom Rini
2020-07-21 22:54   ` Vagrant Cascadian [this message]
2020-07-22 18:32 ` Heinrich Schuchardt
2020-07-22 18:44   ` Tom Rini
2020-07-22 20:40     ` Fabio Estevam
2020-07-22 21:10       ` Tom Rini
2020-07-26 14:57         ` Fabio Estevam
2020-07-26 15:05           ` Tom Rini
2020-07-26 17:00             ` Fabio Estevam
2020-07-26 17:15               ` Tom Rini
2020-07-26 17:56                 ` Fabio Estevam
2020-07-26 18:17                   ` Vagrant Cascadian
2020-07-26 18:22                     ` Fabio Estevam
2020-07-28 11:23                     ` Fabio Estevam

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=87k0yw7a3o.fsf@ponder \
    --to=vagrant@reproducible-builds.org \
    --cc=u-boot@lists.denx.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