linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <davidb@codeaurora.org>
To: Samuel Omlin <samuel.omlin@gmail.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: Terms of MSM/QSD in QAEP
Date: Mon, 5 Mar 2012 08:35:21 -0800	[thread overview]
Message-ID: <20120305163521.GA5302@codeaurora.org> (raw)
In-Reply-To: <CAJPDVo8i2qrPLJ77Dk0kSqaJqUnmn5XAHj6vnK9qEYyftrt8Nw@mail.gmail.com>

On Sat, Mar 03, 2012 at 10:51:40AM +0800, Samuel Omlin wrote:
> Hi David,
> 
> Thank you for your reply quickly.
> 
> As far as I can know, all parts after the name of chipset (like
> msm7630) indicate that what case the chipset is applied to. Let's say,
> CSFB short for Circuit Switch Fall Back in the naming of xxxxxx_csfb
> means being with the functionality of LTE in the modem side for the
> chipset. In other words, it is exactly available when required to
> support LTE on the air. Note that xxxxxxx here stands for chipset name
> that looks something like msm7630.
> 
> So, all i would like to know is what situations those "fusion" and
> "surf" and "ffa" for chipesets like msm7630  are applied tor,
> separately. That's it.

They are the names of particular boards that have the msm7630 chip on
them.  My guess is that they would be used when building for that
specific target.

David

> Thanks a lot.
> 
> 
> Best Regards,
> Samuel
> 
> 
> 
> On Thu, Mar 1, 2012 at 5:18 AM, David Brown <davidb@codeaurora.org> wrote:
> > On Wed, Feb 29, 2012 at 11:21:51PM +0800, Samuel Omlin wrote:
> >> Hi CodeAurora,
> >>
> >> While going through the whole source code by the GitWeb interface
> >> (https://www.codeaurora.org/gitweb/quic/la/), there are so many very
> >> obscure terms of MSM/QSD chipset in QAEP (MSM/QSD Android Enablement
> >> Project) making people stuck out there, who are trying being aware of
> >> exactly what they indicate like me, as below.
> >> platform/vendor/qcom/msm7625_ffa.git
> >> platform/vendor/qcom/msm7625_surf.git
> >>
> >> platform/vendor/qcom/msm7627_6x.git
> >> platform/vendor/qcom/msm7627_7x_ffa.git
> >> platform/vendor/qcom/msm7627_7x_surf.git
> >> platform/vendor/qcom/msm7627_ffa.git
> >> platform/vendor/qcom/msm7627_surf.git
> >> platform/vendor/qcom/msm7627a.git
> >>
> >> platform/vendor/qcom/msm7630_1x_surf.git
> >> platform/vendor/qcom/msm7630_ffa.git
> >> platform/vendor/qcom/msm7630_fusion.git
> >> platform/vendor/qcom/msm7630_surf.git
> >>
> >> platform/vendor/qcom/msm8660_csfb.git
> >> platform/vendor/qcom/msm8660_surf.git
> >>
> >> platform/vendor/qcom/msm8960.git
> >>
> >> platform/vendor/qcom/qsd8250_ffa.git
> >> platform/vendor/qcom/qsd8250_surf.git
> >> platform/vendor/qcom/qsd8650a_st1x.git
> >>
> >> Therefore, here are couple of questions come up with:
> >> 1> What do FFA, SURF and Fusion for MSM/QSD stand for, individually?
> >
> > The simple answer is that MSM/QSD are the names of the Qualcomm SoC,
> > such as MSM8660.  There was one family that used the QSD prefix
> > (8250/8660), but these are otherwise just part of the family.
> >
> > Terms such as FFA, SURF, and Fusion are names of particular boards
> > that use these chips.  These are generally dev boards, and
> > unfortunately, most are not readily available.  The SURF is usually a
> > larger dev-board, whereas the other targets are usually a smaller form
> > factor.
> >
> > David
> >
> > --
> > Sent by an employee of the Qualcomm Innovation Center, Inc.
> > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

      reply	other threads:[~2012-03-05 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 15:21 Terms of MSM/QSD in QAEP Samuel Omlin
2012-02-29 21:18 ` David Brown
2012-03-03  2:51   ` Samuel Omlin
2012-03-05 16:35     ` David Brown [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=20120305163521.GA5302@codeaurora.org \
    --to=davidb@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=samuel.omlin@gmail.com \
    /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).