[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <c991ca40-5b9d-45fd-a4e8-4fe6930c2968@app.fastmail.com>
Date: Wed, 12 Jun 2024 17:57:55 +0100
From: "Jiaxun Yang" <jiaxun.yang@...goat.com>
To: "Conor Dooley" <conor@...nel.org>
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
在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.
Thanks
>
> 附件:
> * signature.asc
--
- Jiaxun
Powered by blists - more mailing lists