public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Quentin Schulz <quentin.schulz@cherry.de>,
	Fabio Estevam <festevam@gmail.com>
Cc: Hendrik Donner <hd@os-cillation.de>,
	u-boot@lists.denx.de, Stefano Babic <sbabic@denx.de>,
	"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
	Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH 1/2] imx8qxp: Do not use CONFIG_XPL_BUILD in device tree
Date: Mon, 17 Mar 2025 07:40:45 -0600	[thread overview]
Message-ID: <20250317134045.GL2640854@bill-the-cat> (raw)
In-Reply-To: <a872429d-7ba5-4936-b496-c80af4444d4e@cherry.de>

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

On Mon, Mar 17, 2025 at 12:10:04PM +0100, Quentin Schulz wrote:
> Hi Fabio,
> 
> On 3/15/25 12:58 PM, Fabio Estevam wrote:
> > Hi Hendrik,
> > 
> > On Fri, Mar 14, 2025 at 5:09 PM Hendrik Donner <hd@os-cillation.de> wrote:
> > > 
> > > In c9713c155127 the device tree was moved
> > > from CONFIG_SPL to CONFIG_SPL_BUILD and later to CONFIG_XPL_BUILD, but
> > > the CONFIG_xPL_BUILD defines are never set for device trees, breaking
> > > the build. Move the guards back to CONFIG_SPL.
> > 
> > Please provide details about the "breaking the build". Which target
> 
> The nodes will simply never be added, because CONFIG_XPL_BUILD (or
> CONFIG_SPL_BUILD) simply aren't passed to dtc.
> 
> So essentially, this is equivalent to dead/noop code.
> 
> > fails to build currently?
> > 
> > After applying this series, the previous build failures return:
> > 
> 
> Yes, it was never fixed, just silenced by never building it.
> 
> See https://lore.kernel.org/u-boot/2849ff05-ef67-4471-aece-422daa57040f@cherry.de/

It sounds to me like imx8/9 and faking external blobs isn't being
handled correctly at this time. Along with needing to make use of
making use of CONFIG_BUILD_TARGET so that "make all" will build the
right binary (when the right external blobs exist).

-- 
Tom

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

  parent reply	other threads:[~2025-03-17 13:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 18:35 [PATCH 0/2] Build fixes for CONFIG_XPL_BUILD in dts files Hendrik Donner
2025-03-05 18:35 ` [PATCH 1/2] imx8qm: Fix build when using SPL Hendrik Donner
2025-03-05 18:35 ` [PATCH 2/2] Makefile.lib: Set xPL build related defines for DTB build Hendrik Donner
2025-03-06 10:18   ` Quentin Schulz
2025-03-06 10:22     ` Oliver Graute
2025-03-06 16:28     ` Hendrik Donner
2025-03-06 17:40       ` Quentin Schulz
2025-03-14 20:08         ` [PATCH 0/2] Do not use CONFIG_XPL_BUILD in device tree Hendrik Donner
2025-03-14 20:08           ` [PATCH 1/2] imx8qxp: " Hendrik Donner
2025-03-15 11:58             ` Fabio Estevam
2025-03-17 11:10               ` Quentin Schulz
2025-03-17 12:41                 ` Hendrik Donner
2025-03-17 13:40                 ` Tom Rini [this message]
2025-03-14 20:08           ` [PATCH 2/2] imx8qm: " Hendrik Donner
2025-03-06 17:56       ` [PATCH 2/2] Makefile.lib: Set xPL build related defines for DTB build Simon Glass

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=20250317134045.GL2640854@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=festevam@gmail.com \
    --cc=hd@os-cillation.de \
    --cc=quentin.schulz@cherry.de \
    --cc=sbabic@denx.de \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.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