linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Omlin <samuel.omlin@gmail.com>
To: linux-arm-msm@vger.kernel.org
Cc: samuel omlin <samuel.omlin@gmail.com>
Subject: Terms of MSM/QSD in QAEP
Date: Wed, 29 Feb 2012 23:21:51 +0800	[thread overview]
Message-ID: <CAJPDVo_pVHmty2kx1FC8fQ83VJOsrASnPQrArPf+bu4adOGzmw@mail.gmail.com> (raw)

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?
2> What features for FFA, SURF and Fusion for MSM/QSD, separately?


Best Regards,
Samuel

             reply	other threads:[~2012-02-29 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 15:21 Samuel Omlin [this message]
2012-02-29 21:18 ` Terms of MSM/QSD in QAEP David Brown
2012-03-03  2:51   ` Samuel Omlin
2012-03-05 16:35     ` David Brown

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=CAJPDVo_pVHmty2kx1FC8fQ83VJOsrASnPQrArPf+bu4adOGzmw@mail.gmail.com \
    --to=samuel.omlin@gmail.com \
    --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).