<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Andrew Lunn 於 1/21/2026 6:10 AM 寫道:<br>
</div>
<blockquote type="cite"
cite="mid:2e3f213b-d507-4290-91af-fba7492155d2@lunn.ch">
<pre class="moz-quote-pre" wrap="">Does ma35d1.dtsi represent the SOM?</pre>
</blockquote>
ma35d1.dtsi describes the MA35D1 SoC and its integrated peripherals
only.<br>
It does not describe any board-level components and is not a SOM
description.<br>
<blockquote type="cite"
cite="mid:2e3f213b-d507-4290-91af-fba7492155d2@lunn.ch">
<pre class="moz-quote-pre" wrap="">
If so, what is ma35d1-som-256m.dts ? It looks like some odd sort of
carrier board with a few serial ports and some memory? But systems
like this put the memory on the SOM, not the carrier.</pre>
</blockquote>
In our hardware design, the DDR memory is part of the board itself.<br>
For the SOM-based product, the memory resides on the SOM module;
therefore, it is described in the corresponding board .dts file.<br>
Although we use "SOM" terminology internally, from a hardware and
device tree perspective these are single-board designs,<br>
and all <code data-start="2948" data-end="2954">.dts</code> files
describe complete boards.
<blockquote type="cite"
cite="mid:2e3f213b-d507-4290-91af-fba7492155d2@lunn.ch">
<pre class="moz-quote-pre" wrap="">
As i said, i'm confused with your naming here.</pre>
</blockquote>
<p>Best regards,</p>
<p>Joey<br>
</p>
<blockquote type="cite"
cite="mid:2e3f213b-d507-4290-91af-fba7492155d2@lunn.ch">
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
</body>
</html>