All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: [OT?] where to start building for qualcomm snapdragon APQ8016E dragonboard 410C?
Date: Thu, 11 May 2017 06:48:23 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1705110623380.31743@localhost.localdomain> (raw)


  (i'm sure there's a more appropriate forum to ask this, but i'm just
going to throw myself on the mercy of the general OE list.)

  i've been asked to help out with lashing together an OE build for a
target board that will be based on qualcomm's snapdragon 410 APQ8016E,
so the obvious choice for an initial reference system would be the
96boards.org-approved dragonboard 410c from arrow (i'm open to other
suggestions for more fully-featured boards supported by OE):

 http://www.96boards.org/product/dragonboard410c/

but, wow, are there a bunch of places to start pulling content from.

  i picked out the meta-qcom layer immediately:

 http://git.yoctoproject.org/cgit/cgit.cgi/meta-qcom

which has a machine definition for that very board, and i built a
core-image-minimal image for that target with no trouble (have not
loaded and tested yet, board supposedly arrives tomorrow). so far, so
good. but when i perused further, i found all sorts of URLs with more
info/content/layers, depending on what you were after:

 git://git.linaro.org/landing-teams/working/qualcomm/kernel.git
 https://www.codeaurora.org/openembedded-mass-market-and-ioe-qualcomm-snapdragon
 https://developer.qualcomm.com/hardware/dragonboard-410c
 https://github.com/96boards/
 https://createpoint.qti.qualcomm.com/

and i'm not sure that's even the entire list i've seen.

  specifically, i'm wondering where the canonical code base is for
what i'm doing, and i was told that it's at that qualcomm location,
for which one needs an account. a colleague has an account and let me
peruse the qualcomm createpoint repo, but it seems that whatever i see
there is available publicly, particularly at codeaurora.org.

  can someone clarify how all these sites hang together, and where one
starts? as i said, right now, the meta-qcom layer works right out of
the box to build an image for that target. is it necessary to get
access to qualcomm's createpoint repo? or is everything i might need
available publicly at github and codeaurora?

  thanks for any pointers.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


             reply	other threads:[~2017-05-11 10:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 10:48 Robert P. J. Day [this message]
2017-05-11 12:22 ` [OT?] where to start building for qualcomm snapdragon APQ8016E dragonboard 410C? Nicolas Dechesne
2017-05-11 16:43   ` Khem Raj
2017-05-11 16:48     ` Nicolas Dechesne
2017-05-11 16:50       ` Khem Raj

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=alpine.LFD.2.20.1705110623380.31743@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@lists.openembedded.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 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.