* What is the Surf board , really?
@ 2016-06-02 6:25 ` Linus Walleij
0 siblings, 0 replies; 6+ messages in thread
From: Linus Walleij @ 2016-06-02 6:25 UTC (permalink / raw)
To: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Stephen Boyd,
Bjorn Andersson, Andy Gross
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.
So before I go patching it around, should I work on this DTS file
or create a new one for the DragonBoard APQ8660?
Yours,
Linus Walleij
^ permalink raw reply [flat|nested] 6+ messages in thread
* What is the Surf board , really?
@ 2016-06-02 6:25 ` Linus Walleij
0 siblings, 0 replies; 6+ messages in thread
From: Linus Walleij @ 2016-06-02 6:25 UTC (permalink / raw)
To: linux-arm-kernel
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.
So before I go patching it around, should I work on this DTS file
or create a new one for the DragonBoard APQ8660?
Yours,
Linus Walleij
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: What is the Surf board , really?
2016-06-02 6:25 ` Linus Walleij
@ 2016-06-02 16:31 ` Hartley Sweeten
-1 siblings, 0 replies; 6+ messages in thread
From: Hartley Sweeten @ 2016-06-02 16:31 UTC (permalink / raw)
To: Linus Walleij, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Stephen Boyd,
Bjorn Andersson, Andy Gross
On Wednesday, June 01, 2016 11:25 PM, 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.
I think the APQ8x60 is a MSM8x60 variant without a modem. So
the APQ parts are "application processors" and the MSM parts are
"phone processors". Other than that I think they are the same.
But I could be total wrong....
Hartley
^ permalink raw reply [flat|nested] 6+ messages in thread
* What is the Surf board , really?
@ 2016-06-02 16:31 ` Hartley Sweeten
0 siblings, 0 replies; 6+ messages in thread
From: Hartley Sweeten @ 2016-06-02 16:31 UTC (permalink / raw)
To: linux-arm-kernel
On Wednesday, June 01, 2016 11:25 PM, 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.
I think the APQ8x60 is a MSM8x60 variant without a modem. So
the APQ parts are "application processors" and the MSM parts are
"phone processors". Other than that I think they are the same.
But I could be total wrong....
Hartley
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: What is the Surf board , really?
2016-06-02 6:25 ` Linus Walleij
@ 2016-06-02 18:04 ` Stephen Boyd
-1 siblings, 0 replies; 6+ messages in thread
From: Stephen Boyd @ 2016-06-02 18:04 UTC (permalink / raw)
To: Linus Walleij
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Bjorn Andersson, Andy Gross
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* What is the Surf board , really?
@ 2016-06-02 18:04 ` Stephen Boyd
0 siblings, 0 replies; 6+ messages in thread
From: Stephen Boyd @ 2016-06-02 18:04 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-06-02 18:04 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-06-02 6:25 What is the Surf board , really? Linus Walleij
2016-06-02 6:25 ` Linus Walleij
2016-06-02 16:31 ` Hartley Sweeten
2016-06-02 16:31 ` Hartley Sweeten
2016-06-02 18:04 ` Stephen Boyd
2016-06-02 18:04 ` Stephen Boyd
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.