From: Stephen Boyd <sboyd@codeaurora.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <andy.gross@linaro.org>
Subject: Re: What is the Surf board , really?
Date: Thu, 2 Jun 2016 11:04:29 -0700 [thread overview]
Message-ID: <20160602180429.GJ28218@codeaurora.org> (raw)
In-Reply-To: <CACRpkdYtHWObewx6vJXbPU9Wv4rhR0i7sW9YB0Ap8yo5aTJy=Q@mail.gmail.com>
On 06/02, Linus Walleij wrote:
> I located all my schematics to the APQ8660 DragonBoard thing.
>
> Now: is the "surf" board one and the same as this? I never really
> got that confirmed. It's got the msm8660 rather than apq8660
> naming and all so I get confused.
>
> So I was thinking that surf is maybe some other (phone) development
> board.
The surf is an internal development platform that is not the same
as the apq8060 dragonboard. So you're right, they're different.
I'm not aware of any msm8660 dragonboard device in existence, so
it really is an apq8060 chip on there from what I know.
>
> So before I go patching it around, should I work on this DTS file
> or create a new one for the DragonBoard APQ8660?
>
I would make a new one that reuses the msm8660.dtsi file and then
does the board specific things.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-06-02 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 6:25 What is the Surf board , really? Linus Walleij
2016-06-02 16:31 ` Hartley Sweeten
2016-06-02 18:04 ` Stephen Boyd [this message]
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=20160602180429.GJ28218@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@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;
as well as URLs for NNTP newsgroup(s).