From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Neal Frager via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1 1/1] configs/zynqmp_kria_kv260_defconfig: fix linux dts name
Date: Mon, 19 Dec 2022 13:36:20 +0100 [thread overview]
Message-ID: <20221219133620.396349dc@booty> (raw)
In-Reply-To: <CH2PR12MB50045ED2EDE0ABD845FC8D8CF0E29@CH2PR12MB5004.namprd12.prod.outlook.com>
On Mon, 12 Dec 2022 13:47:29 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> Hi Thomas,
>
> > And in fact, it seems this patch is also broken: there is no Device Tree named zynqmp-smk-k26-revA-sck-kv-g-revB.dts:
>
> > $ make zynqmp_kria_kv260_defconfig
> > $ make linux-patch
> > $ find output/build/linux-custom/ -name 'zynqmp-smk-k26-revA-sck-kv-g-revB.dts'
>
> > I have done a full build and run test on all of these patches you have been committing, including this one.
>
> In case my last message was not absolutely clear, the mistake I made when updating the zynqmp_kria_kv260_defconfig from Xilinx 2022.1 to 2022.2 was not handling the device tree name change.
>
> 2022.1 used smk-k26-revA-sck-kv-g-revB.dtb
> https://github.com/Xilinx/linux-xlnx/blob/xlnx_rebase_v5.15_2022.1/arch/arm64/boot/dts/xilinx/Makefile
> smk-k26-revA-sck-kv-g-revB-dtbs := zynqmp-smk-k26-revA.dtb zynqmp-sck-kv-g-revB.dtbo
> dtb-$(CONFIG_ARCH_ZYNQMP) += smk-k26-revA-sck-kv-g-revB.dtb
>
> 2022.2 changed to zynqmp-smk-k26-revA-sck-kv-g-revB.dtb
> https://github.com/Xilinx/linux-xlnx/blob/xlnx_rebase_v5.15_2022.2/arch/arm64/boot/dts/xilinx/Makefile
> zynqmp-smk-k26-revA-sck-kv-g-revB-dtbs := zynqmp-smk-k26-revA.dtb zynqmp-sck-kv-g-revB.dtbo
> dtb-$(CONFIG_ARCH_ZYNQMP) += zynqmp-smk-k26-revA-sck-kv-g-revB.dtb
>
> In both cases, the defconfig remains the default zynqmp xilinx_zynqmp_virt_defconfig which is used for all zynqmp builds.
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-12-19 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 12:48 [Buildroot] [PATCH v1 1/1] configs/zynqmp_kria_kv260_defconfig: fix linux dts name Neal Frager via buildroot
2022-12-11 17:03 ` Thomas Petazzoni via buildroot
2022-12-11 17:55 ` Frager, Neal via buildroot
2022-12-12 13:47 ` Frager, Neal via buildroot
2022-12-19 12:36 ` Luca Ceresoli via buildroot [this message]
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=20221219133620.396349dc@booty \
--to=buildroot@buildroot.org \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=thomas.petazzoni@bootlin.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.