From: Tom Rini <trini@konsulko.com>
To: Sune Brian <briansune@gmail.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v6] Add optimized Makefile support for SoCFPGA handoff
Date: Tue, 4 Nov 2025 17:07:45 -0600 [thread overview]
Message-ID: <20251104230745.GK6688@bill-the-cat> (raw)
In-Reply-To: <CAN7C2SDnm5cK-J=DocOk5hS8k_7565RB9yg5XNVu_kaNb3UjvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Wed, Nov 05, 2025 at 06:48:19AM +0800, Sune Brian wrote:
> > Yes, it really needs to not be in the top level Makefile, the more stuff
> > we have there the trickier upstream merges get, especially when this can
> > be hooked to archprepare and work just fine. Thanks.
>
> Done~ see v7
>
> Now back to the documentation you want.
> Where and what should be included.
> If possible, a good example can help me settle things faster.
Well, doc/board/ti/, doc/board/nxp/ and doc/board/rockchip are all good
examples of how different SoCs have provided a pretty good level of
documentation, some of which includes various external blobs or tools to
also use. That might be a good starting point for better documenting
socfpga and then also including using this tool.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-04 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 1:00 [PATCH v6] Add optimized Makefile support for SoCFPGA handoff Brian Sune
2025-11-04 17:51 ` Tom Rini
2025-11-04 20:42 ` Sune Brian
2025-11-04 21:18 ` Tom Rini
2025-11-04 21:33 ` Sune Brian
2025-11-04 22:37 ` Tom Rini
2025-11-04 22:48 ` Sune Brian
2025-11-04 23:07 ` Tom Rini [this message]
2025-11-04 23:30 ` Sune Brian
2025-11-04 21:11 ` 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=20251104230745.GK6688@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