From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>,
Brandon Maier <brandon.maier@collins.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>,
"romain.naour@smile.fr" <romain.naour@smile.fr>,
"Simek, Michal" <michal.simek@amd.com>,
"yann.morin.1998@free.fr" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v2 1/1] board/xilinx: bump to linux 6.6.40
Date: Fri, 9 Aug 2024 08:30:13 +0200 [thread overview]
Message-ID: <20240809083013.05d0d0fc@windsurf> (raw)
In-Reply-To: <CH2PR12MB50043F73B67812E0158B2C2CF0BA2@CH2PR12MB5004.namprd12.prod.outlook.com>
On Fri, 9 Aug 2024 03:52:30 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> I can help you with this problem. It is because there are two different
> versions of the zcu106 having different DDR memories. This is because the
> DDR that came on the revA version of the board became obsolete.
>
> I left the revA device tree in buildroot as I know this is the version of the
> zcu106 that Peter Korsgaard has. Based on your comment, I believe you have
> the newer version of the zcu106.
>
> To fix this, only the u-boot psu_init_gpl.c needs to be changed, so the
> correct spl psu_init routine will run.
>
> Please implement the following in your zcu106 defconfig:
>
> - BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS="DEVICE_TREE=zynqmp-zcu106-revA
> + BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS="DEVICE_TREE=zynqmp-zcu106-rev1.0
>
> This will build in the correct psu_init_gpl.c from the two choices below:
> https://github.com/Xilinx/u-boot-xlnx/tree/master/board/xilinx/zynqmp/zynqmp-zcu106-rev1.0
> https://github.com/Xilinx/u-boot-xlnx/tree/master/board/xilinx/zynqmp/zynqmp-zcu106-revA
>
> You can read about this issue for the zcu102 and zcu106 here:
> https://support.xilinx.com/s/article/71961?language=en_US
>
> Do you have any opinions for how this can be better handled in buildroot to
> support both versions of the zcu102 and zcu106?
The only nice option from a Buildroot perspective would be to runtime
detect the board revision in U-Boot and apply the correct DDR
configuration accordingly. This way a single image would work on both
revisions. Having two full defconfigs to address those two board
revisions would be a bit annoying.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-09 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 13:23 [Buildroot] [PATCH v2 1/1] board/xilinx: bump to linux 6.6.40 Neal Frager via buildroot
2024-08-08 19:44 ` Brandon Maier via buildroot
2024-08-09 3:52 ` Frager, Neal via buildroot
2024-08-09 6:30 ` Thomas Petazzoni via buildroot [this message]
2024-08-09 6:39 ` Frager, Neal via buildroot
[not found] ` <3036afae-2027-4993-bb1f-acd3b312759e@amd.com>
2024-08-09 8:22 ` Frager, Neal via buildroot
2024-08-09 15:02 ` Brandon Maier via buildroot
2024-08-09 15:19 ` Frager, Neal via buildroot
2024-08-19 10:01 ` Luca Ceresoli via buildroot
2024-08-09 15:51 ` Brandon Maier via buildroot
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=20240809083013.05d0d0fc@windsurf \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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