[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240722-cuddly-valiant-ba6153953190@wendy>
Date: Mon, 22 Jul 2024 12:12:21 +0100
From: Conor Dooley <conor.dooley@...rochip.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
CC: <ysionneau@...rayinc.com>, <linux-kernel@...r.kernel.org>, Rob Herring
<robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Jonathan Borne <jborne@...rayinc.com>, Julian Vetter
<jvetter@...rayinc.com>, <devicetree@...r.kernel.org>
Subject: Re: [RFC PATCH v3 36/37] kvx: dts: DeviceTree for qemu emulated
Coolidge SoC
On Mon, Jul 22, 2024 at 11:55:46AM +0200, Krzysztof Kozlowski wrote:
> On 22/07/2024 11:41, ysionneau@...rayinc.com wrote:
> > From: Yann Sionneau <ysionneau@...rayinc.com>
> >
> > Add device tree for QEMU that emulates a Coolidge V1 SoC.
> > + model = "Kalray Coolidge processor (QEMU)";
> > + compatible = "kalray,coolidge-qemu";
I'm not sure that this should even be in the kernel. Why isn't QEMU able
to generate a devicetree for this emulated platform, like it can on
other architectures?
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists