From: Rutherther via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] PYNQ Z2: new board support contribution question
Date: Thu, 01 May 2025 16:15:42 +0200 [thread overview]
Message-ID: <87ecx8ju29.fsf@ditigal.xyz> (raw)
In-Reply-To: <87h624jv62.fsf@ditigal.xyz>
Hello,
I have made support for Pynq Z2 board locally (though most of it is off
of work of others that submitted patch to u-boot), and wanted to
contribute it.
The thing is, this board is not supported in u-boot / linux, at least
not yet. This means that the device tree and ps7 init have to be added
to buildroot in order to support it, so I wanted to ask:
1. Is it fine to put those files to buildroot, or does the support first
have to come in u-boot/linux in order for buildroot to support it as well?
2. If so, what way is preferred:
a. Patches for u-boot and linux
b. Set custom path to ps7 init and device tree
Currently I have it implemented as a. It will probably be a bit harder
to do with u-boot with b as I am not sure how to pass the device tree
file from buildroot to u-boot, with linux it's clear.
Thanks,
Rutherther
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
parent reply other threads:[~2025-05-01 14:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87h624jv62.fsf@ditigal.xyz>]
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=87ecx8ju29.fsf@ditigal.xyz \
--to=buildroot@buildroot.org \
--cc=rutherther@ditigal.xyz \
/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