mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Michael Tretter <m.tretter@pengutronix.de>
To: Johannes Roith <johannes@gnu-linux.rocks>
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: Barebox for Zedboard
Date: Mon, 26 May 2025 09:23:44 +0200	[thread overview]
Message-ID: <aDQXAEr1fl0wgV4k@pengutronix.de> (raw)
In-Reply-To: <933c22ee-bafe-4736-80bc-0674d7782124@pengutronix.de>

On Mon, 19 May 2025 06:55:52 +0200, Ahmad Fatoum wrote:
> On 18.05.25 19:06, Johannes Roith wrote:
> > Am Fri, May 16, 2025 at 09:28:03PM +0200 schrieb Ahmad Fatoum:
> >> Loading OF overlays can already load firmware that way.
> > 
> > Could you give me an example for an OF overlay to load a firmware?
> 
> Should look the same as in Linux (with overlay patches applied).
> 
> Michael, do you happen to have an example to share?

The overlay looks the same as in Linux and documented in
fpga-region.yaml.

For example, if your device tree contains a node with a fpga-region for
the fpga named fpga_full and the fpga-mgr property has a phandle to the
node of the FPGA Manager, the following overlay should instruct the FPGA
Manager to load the bitstream.bit firmware into the FPGA.

	/dts-v1/;
	/plugin/;
	&fpga_full {
		firmware-name = "bitstream.bin";
	};

In the overlay you should also describe the gateware implemented in the
bitstream. This allows Linux to detect what's actually implemented in
the bitstream and probe the proper drivers.

Michael



  reply	other threads:[~2025-05-26  7:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 10:38 Michael Graichen
2020-03-19 10:53 ` Lucas Stach
2020-03-23 14:22   ` AW: " Michael Graichen
2020-03-23 15:18   ` Michael Graichen
2025-05-16 19:03     ` Johannes Roith
2025-05-16 19:28       ` Ahmad Fatoum
2025-05-18 17:06         ` Johannes Roith
2025-05-19  4:55           ` Ahmad Fatoum
2025-05-26  7:23             ` Michael Tretter [this message]
2025-05-19  6:50           ` AW: " Michael Graichen
2025-05-19 18:41             ` Johannes Roith
2025-05-19 19:56               ` Ahmad Fatoum

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=aDQXAEr1fl0wgV4k@pengutronix.de \
    --to=m.tretter@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=johannes@gnu-linux.rocks \
    /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