[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240612-purr-tribute-6842361c9815@spud>
Date: Wed, 12 Jun 2024 17:59:41 +0100
From: Conor Dooley <conor@...nel.org>
To: Jiaxun Yang <jiaxun.yang@...goat.com>
Cc: Lee Jones <lee@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
"paulburton@...nel.org" <paulburton@...nel.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>
Subject: Re: [PATCH v2 8/8] dt-bindings: mips: img: Add devices binding
On Wed, Jun 12, 2024 at 05:57:55PM +0100, Jiaxun Yang wrote:
>
>
> 在2024年6月12日六月 下午5:43,Conor Dooley写道:
> [...]
> > Usually the order used here is something like:
> > compatible = "vendor,soc-board", "vendor,soc"
> > The pistachio one seems to follow that, but AFAICT "boston" is a board
> > and the order in this one is something like:
> > compatible = "vendor,soc", "vendor,generic-fpga-board"
>
> Boston is an FPGA & Emulation platform, so I don't have a good answer
> for what should I fill as SoC.
Ah right. Probably worth adding a little more information then as to
what the platforms are in the commit message in that case.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists