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 14:09:59 -0600	[thread overview]
Message-ID: <20251103200959.GR6688@bill-the-cat> (raw)
In-Reply-To: <CAN7C2SB0b_YjcJ+LyVUJwi5DjdjR5Ssi=yQwuCvSvBh3XVj+dA@mail.gmail.com>

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

On Tue, Nov 04, 2025 at 02:55:53AM +0800, Sune Brian wrote:
> > OK. I was hoping that we could just automate as part of the regular
> > build process seeing for example $(BOARD)/foo.xml and invoking the
> > script to re-create foo.c and so forth, but that doesn't seem to be the
> > case. So, no Makefile logic. We should then instead start on some
> > content for doc/board/socfpga/ and document this tool there. Thanks!
> 
> Ok what you expected on the automation flow.
> I can give it a try. But the build flow for Altera project side
> is that the compiled handoff is in the form of a folder.
> only foo_bar is defined by user other naming on C5
> should be fixed.
> 
> hps_isw_handoff/foo_bar/
> 
> |-- alt_types.h
> |-- foo_bar.hiof
> |-- emif.xml
> |-- hps.xml
> |-- id
> |-- sdram_io.h
> |-- sequencer.c
> |-- sequencer.h
> |-- sequencer_auto.h
> |-- sequencer_auto_ac_init.c
> |-- sequencer_auto_inst_init.c
> |-- sequencer_defines.h
> |-- system.h
> |-- tclrpt.c
> `-- tclrpt.h
> 
> Documentation is not an issue.

OK, yes, I think we just document for ourselves too that the tool exists
and how it's expected to be run. Thanks.

-- 
Tom

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

  reply	other threads:[~2025-11-03 20:10 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 [this message]
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
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=20251103200959.GR6688@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