From: Yann Sionneau <ysionneau@kalrayinc.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>, barebox@lists.infradead.org
Cc: jvetter@kalrayinc.com, jborne@kalrayinc.com
Subject: Re: [PATCH 1/3] kvx: add qemu dts
Date: Tue, 13 Aug 2024 08:35:45 +0200 [thread overview]
Message-ID: <accdaf16-42f1-4db9-9343-302c64f6bb61@kalrayinc.com> (raw)
In-Reply-To: <520a960f-7adb-403b-a2c5-ee608177b7ff@pengutronix.de>
Hello Ahmad,
On 13/08/2024 08:28, Ahmad Fatoum wrote:
> On 12.08.24 16:41, Yann Sionneau wrote:
>> obj-$(CONFIG_BOARD_K200) += k200.dtb.o
>> +obj-$(CONFIG_BOARD_QEMU) += qemu.dtb.o
> Given that you pass in the device tree externally anyway, how
> about yo make this obj- an extra-y and drop the Kconfig change.
> That way, the device tree is always generated alongside the
> normal image.
Ack!
>
>>
>> clean-files := *.dtb *.dtb.S .*.dtc .*.pre .*.dts *.dtb.z
>> diff --git a/arch/kvx/dts/qemu.dts b/arch/kvx/dts/qemu.dts
>> new file mode 100644
>> index 0000000000..68d242c113
>> --- /dev/null
>> +++ b/arch/kvx/dts/qemu.dts
>> @@ -0,0 +1,269 @@
>> +/dts-v1/;
>> +
>> +/ {
>> + model = "Kalray Coolidge processor (QEMU)";
>> + #address-cells = <0x02>;
>> + #size-cells = <0x02>;
>> + compatible = "kalray,coolidge\0kalray,iss";
> Is this a decompiled device tree?
Yes, you got me ^^ I replaced all hard-coded phandles with label references but I forgot about splitting this compatible into 2 strings. Will do!
I used the generated dtb from qemu as source for this patch by doing `kvx-system-qemu -M mppa-coolidge,dumpdtb=qemu.dtb`
Regards,
--
Yann
prev parent reply other threads:[~2024-08-13 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 14:41 Yann Sionneau
2024-08-12 14:41 ` [PATCH 2/3] ci: container: add qemu-system-kvx Yann Sionneau
2024-08-12 14:41 ` [PATCH 3/3] ci: add support for running basic tests on kvx arch Yann Sionneau
2024-08-13 6:25 ` Ahmad Fatoum
2024-08-13 6:36 ` Yann Sionneau
2024-08-13 6:28 ` [PATCH 1/3] kvx: add qemu dts Ahmad Fatoum
2024-08-13 6:35 ` Yann Sionneau [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=accdaf16-42f1-4db9-9343-302c64f6bb61@kalrayinc.com \
--to=ysionneau@kalrayinc.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jborne@kalrayinc.com \
--cc=jvetter@kalrayinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox