From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <nealf@xilinx.com>
Cc: "luca@lucaceresoli.net" <luca@lucaceresoli.net>,
"giulio.benetti@benettiengineering.com"
<giulio.benetti@benettiengineering.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>,
"michal.simek@amd.com" <michal.simek@amd.com>,
Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v1 1/2] add configs/zynqmp_kria_kv260_defconfig
Date: Sat, 07 May 2022 23:01:29 +0200 [thread overview]
Message-ID: <87czgpys46.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <BE2A1487-0690-4BE3-BFEA-AC439B98FD3D@xilinx.com> (Neal Frager's message of "Sat, 7 May 2022 06:26:28 +0000")
>>>>> "Neal" == Neal Frager <nealf@xilinx.com> writes:
Hi,
>> Are you planning to also support other kria boards given the kria/
>> subdir?
> Yes, there is another Kria carrier board we are about to announce. It
> is not public yet, but I setup the directories in planning for this.
Ahh, sounds interesting ;)
>>
>>> board/zynqmp/kria/post-build.sh | 8 +
>>
>> The post-build.sh copy is not so nice, but ok.
> I agree. If you have a better solution, I would be happy to have any suggestions.
There's a number of options, E.G. we could use a symlink to the existing
script or pass the file to copy as an argument in
BR2_ROOTFS_POST_SCRIPT_ARGS. U-Boot afaik also expands variable
references in the extlinux files, so if there is already a U-Boot
variable with the serial port name then that could be used.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-07 21:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 15:54 [Buildroot] [PATCH v1 1/2] add configs/zynqmp_kria_kv260_defconfig Neal Frager via buildroot
2022-05-05 15:54 ` [Buildroot] [PATCH v1 2/2] DEVELOPERS update Neal Frager via buildroot
2022-05-05 19:49 ` Arnout Vandecappelle
2022-05-06 19:22 ` Peter Korsgaard
2022-05-06 11:17 ` [Buildroot] [PATCH v1 1/2] add configs/zynqmp_kria_kv260_defconfig Wesley Revens
2022-05-06 11:30 ` Neal Frager
[not found] ` <51fb4a8c-cd8c-9db0-76e4-5461e72871f8@xilinx.com>
2022-05-09 6:23 ` Neal Frager
[not found] ` <dd608132-245a-32b7-7d27-f267c1524fee@xilinx.com>
2022-05-09 9:14 ` Wesley Revens
2022-05-09 9:22 ` Neal Frager
2022-05-09 10:54 ` Wesley Revens
2022-05-09 11:00 ` Neal Frager
2022-05-09 11:19 ` Wesley Revens
2022-05-09 13:46 ` Neal Frager
2022-05-09 14:33 ` Wesley Revens
2022-05-09 14:41 ` Neal Frager
2022-05-09 14:58 ` Wesley Revens
2022-05-09 19:01 ` Neal Frager
2022-05-10 4:29 ` Neal Frager
2022-05-10 4:36 ` Neal Frager
2022-05-10 8:22 ` Wesley Revens
2022-05-10 8:26 ` Neal Frager
2022-05-06 19:22 ` Peter Korsgaard
2022-05-07 6:26 ` Neal Frager
2022-05-07 21:01 ` Peter Korsgaard [this message]
2022-05-08 6:46 ` Neal Frager
2022-05-08 9:05 ` Peter Korsgaard
2022-05-10 9:15 ` Neal Frager
[not found] ` <32c2dc3c-10c1-cda7-219f-f3753940f294@xilinx.com>
2022-05-09 8:14 ` Neal Frager
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=87czgpys46.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=luca@lucaceresoli.net \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=nealf@xilinx.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.