U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Tom Rini <trini@konsulko.com>,
	Minda Chen <minda.chen@starfivetech.com>,
	Hal Feng <hal.feng@starfivetech.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Simon Glass <sjg@chromium.org>
Cc: E Shattow <e@freeshell.de>, u-boot@lists.denx.de
Subject: [PATCH v1 0/2] jh7110: starfive: visionfive2 drop setting of $fdtfile
Date: Mon, 21 Apr 2025 23:45:24 -0700	[thread overview]
Message-ID: <20250422064541.635210-1-e@freeshell.de> (raw)

Drop convenience hack that sets default value of $fdtfile on visionfive2
target(s). This is not needed since the JH7110 OF_UPSTREAM migration and is
anyways a duplication of code from SPL that adds friction to maintenance or
adding new variant visionfive2 targets.

If it is still desirable to have default $fdtfile values based on
OF_UPSTREAM dtb filenames then this should be provided further up the code
path in an API and not by duplicating all board detection logic again from
SPL into the main payload.

Users who need to specify $fdtfile may still do so the normal way as
described in U-Boot documentation.

E Shattow (2):
  doc: board: starfive: Drop setting of $fdtfile
  board: starfive: visionfive2: Drop setting of $fdtfile

 .../visionfive2/starfive_visionfive2.c        | 61 -------------------
 doc/board/starfive/milk-v_mars.rst            | 18 ------
 doc/board/starfive/pine64_star64.rst          | 16 -----
 doc/board/starfive/visionfive2.rst            | 18 ------
 4 files changed, 113 deletions(-)


base-commit: cde0050618968aae335dfbc930641656d51ff5d0
-- 
2.49.0


             reply	other threads:[~2025-04-22  6:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  6:45 E Shattow [this message]
2025-04-22  6:45 ` [PATCH v1 1/2] doc: board: starfive: Drop setting of $fdtfile E Shattow
2025-04-22  6:45 ` [PATCH v1 2/2] board: starfive: visionfive2: " E Shattow
2025-04-22  7:28   ` Heinrich Schuchardt
2025-04-22  9:50     ` E Shattow
2025-04-22 10:07   ` E Shattow
2025-04-22 15:17     ` Samuel Holland

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=20250422064541.635210-1-e@freeshell.de \
    --to=e@freeshell.de \
    --cc=hal.feng@starfivetech.com \
    --cc=minda.chen@starfivetech.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --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