Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <nealf@xilinx.com>
Cc: "luca@lucaceresoli.net" <luca@lucaceresoli.net>,
	"giulio.benetti@benettiengineering.com"
	<giulio.benetti@benettiengineering.com>,
	Michal Simek <michals@xilinx.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v6 1/2] configs/zynqmp_zcu106: bump ATF/U-Boot/Linux to Xilinx 2022
Date: Wed, 23 Feb 2022 12:18:17 +0100	[thread overview]
Message-ID: <87fso96dc6.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <PH0PR02MB775035975B305CECD5D842F3D73C9@PH0PR02MB7750.namprd02.prod.outlook.com> (Neal Frager's message of "Wed, 23 Feb 2022 11:02:24 +0000")

>>>>> "Neal" == Neal Frager <nealf@xilinx.com> writes:

Hi,

 > The reason why this was working for me is because I had the DEVICE_TREE environment variable set when building.

 > make distclean
 > make xilinx_zynqmp_virt_defconfig
 > export DEVICE_TREE="zynqmp-zcu106-revA"

I wasn't aware that U-Boot uses the value of this environment variable
over what is speficied in the configuration file. I think we should
clear this environment variable in Buildroot similar to how we do for
E.G. CROSS_COMPILE in the top level Makefile. I'll send a patch for
that.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-02-23 11:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 14:44 [Buildroot] [PATCH v6 1/2] configs/zynqmp_zcu106: bump ATF/U-Boot/Linux to Xilinx 2022 Neal Frager
2022-02-11 14:44 ` [Buildroot] [PATCH v6 2/2] add configs/zynqmp_zcu102_defconfig Neal Frager
2022-02-12 13:43   ` Peter Korsgaard
2022-02-12 13:13 ` [Buildroot] [PATCH v6 1/2] configs/zynqmp_zcu106: bump ATF/U-Boot/Linux to Xilinx 2022 Luca Ceresoli
2022-02-12 13:18   ` Neal Frager
2022-02-12 13:45   ` Peter Korsgaard
2022-02-12 14:47     ` Neal Frager
2022-02-23 10:05     ` Peter Korsgaard
2022-02-23 12:55       ` Neal Frager
2022-02-12 13:42 ` Peter Korsgaard
2022-02-23 10:04   ` Peter Korsgaard
2022-02-23 11:02     ` Neal Frager
2022-02-23 11:11       ` Peter Korsgaard
2022-02-23 11:29         ` Neal Frager
2022-02-23 11:18       ` Peter Korsgaard [this message]
2022-02-23 11:27         ` Neal Frager
2022-02-23 11:07     ` Neal Frager

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=87fso96dc6.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=luca@lucaceresoli.net \
    --cc=michals@xilinx.com \
    --cc=nealf@xilinx.com \
    /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