public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Sune Brian <briansune@gmail.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v2] Add make feature support for SoCFPGA Handoff
Date: Mon, 3 Nov 2025 16:17:12 -0600	[thread overview]
Message-ID: <20251103221712.GT6688@bill-the-cat> (raw)
In-Reply-To: <CAN7C2SACKPnE07-dtwc437f8xr38936h3RWvP1R5Ha_v1KfCng@mail.gmail.com>

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

On Tue, Nov 04, 2025 at 04:50:25AM +0800, Sune Brian wrote:
> > I think I'm not explaining things well enough because I don't quite
> > understand the tooling well enough either. What I would like, but don't
> > think is possible, is something like:
> > $ make O=/tmp/myboard myboard_defconfig
> > ... goes along and sees that boards/myvendor/myboard/myboard.xml exists.
> > ... Runs the python script to re-create all of the C files, assuming xml
> > ... is newer than the C files.
> > ... Now compiles the new C files.
> >
> 
> No, I think your method is just a bit more complex.
> What my last suggestion is just put the handoff folder
> next to qts i.e.
> 
> board/altera/abc/qts
> board/altera/abc/hps_isw_handoff/foo_bar
> 
> Then once you run maybe "make prepare"?
> It generates the new c sets.
> 
> Flow always:
> make xxxx_defconfig
> make prepare <- this is the place it should be automated.
> 
> As the user defines the board then what you need just place
> it new to the qts so it even removes the -o -i user parameter.
> And maybe leave the foo_bar naming for user to enter as
> it could be renamed by the user during the Quartus project build.
> 
> Do you think this is good?

Well, I think so long as you can do "make xxx_defconfig" (and a separate
objdir not source tree), then "make" sees deps and re-runs as needed,
yes, this should be workable. Thanks.

-- 
Tom

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

  reply	other threads:[~2025-11-03 22:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-01  3:52 [PATCH v2] Add make feature support for SoCFPGA Handoff Brian Sune
2025-11-03 15:36 ` Tom Rini
2025-11-03 18:55   ` Sune Brian
2025-11-03 20:09     ` Tom Rini
2025-11-03 20:16       ` Sune Brian
2025-11-03 20:42         ` Tom Rini
2025-11-03 20:50           ` Sune Brian
2025-11-03 22:17             ` Tom Rini [this message]
2025-11-03 22:32               ` Sune Brian

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=20251103221712.GT6688@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=briansune@gmail.com \
    --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