From: "Linas Vepstas (Code Aurora)" <linas@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch@vger.kernel.org, linux-hexagon@vger.kernel.org
Subject: Device trees and systems-on-a-chip
Date: Fri, 23 Sep 2011 12:13:00 -0500 [thread overview]
Message-ID: <20110923171300.GA15815@codeaurora.org> (raw)
Arnd,
Here: http://lwn.net/Articles/457635/ you say: "If the device tree
vision comes true, a single board will actually be able to use the
same device tree binary on either one, independent of which CPU
actually runs the kernel."
In my case, the hexagon and the arm cores will perceive the same
devices at different addresses; there are also devices attached to one
core that aren't attached to the other. So either we have two DT's,
one for each core, or we have one DT with subsections for each core.
I haven't yet looked to see how the DT's are being designed, but I have
this sneaking suspicion that the second alternative is not being
pursued ...
--linas
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next reply other threads:[~2011-09-23 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 17:13 Linas Vepstas (Code Aurora) [this message]
2011-09-23 20:56 ` Device trees and systems-on-a-chip Arnd Bergmann
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=20110923171300.GA15815@codeaurora.org \
--to=linas@codeaurora.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
/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