All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: can one lay hands on a galileo-based dev kit?
Date: Fri, 16 May 2014 08:51:35 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1405160846330.18243@localhost> (raw)
In-Reply-To: <1628239.GfKczbckvq@peggleto-mobl5.ger.corp.intel.com>

On Fri, 16 May 2014, Paul Eggleton wrote:

> So apologies for not replying earlier - I've not been directly
> involved in the BSP for Galileo, but I have been providing support
> for the team doing the IoT DevKit work. You should be able to build
> images for Galileo using what's in meta-intel-iot-devkit directly;
> you could also use the layers within it separately using your own
> separate OE-Core / Poky tree, but it's not really designed to be
> used in that way. If you really want to do it separately you should
> take care to use all three layers (meta-clanton-bsp, meta-galileo,
> and meta-iot-devkit) and set your DISTRO = "iot-devkit".

  possibly a silly question, but what are the dependencies between
those three layers? i'm used to seeing layer dependencies listed in a
layer's "layer.conf" file. if i look at the meta-iot-devkit layer, its
layer.conf file says nothing about dependencies, but one of its kernel
recipes, "linux-yocto-clanton_3.8.bbappend", is clearly a reference to
a kernel recipe in the meta-clanton-bsp layer.

  i would thus have expected to see that dependency listed in the
layer.conf file. has something about listing layer dependencies
changed while i wasn't looking?

rday

-- 

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

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


  parent reply	other threads:[~2014-05-16 12:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 16:34 can one lay hands on a galileo-based dev kit? Robert P. J. Day
2014-04-29 16:43 ` Alex J Lennon
2014-04-29 16:50   ` Robert P. J. Day
2014-04-30  2:43     ` Trevor Woerner
2014-04-30  2:46       ` Trevor Woerner
2014-05-13 13:56   ` Robert P. J. Day
2014-05-13 14:16     ` Vaduva alexandru
2014-05-13 14:20       ` Robert P. J. Day
2014-05-13 14:33     ` Alex J Lennon
2014-05-16 10:11       ` Paul Eggleton
2014-05-16 10:29         ` Alex J Lennon
2014-05-16 10:47           ` Paul Eggleton
2014-05-16 11:17             ` Alex J Lennon
2014-05-16 11:32               ` Paul Eggleton
2014-05-16 12:15                 ` Alex J Lennon
2014-05-16 11:37         ` Robert P. J. Day
2014-05-16 13:29           ` Paul Eggleton
2014-05-16 12:51         ` Robert P. J. Day [this message]
2014-05-16 13:10           ` Paul Eggleton
2014-05-16 13:58             ` Robert P. J. Day
2014-05-13 20:12     ` Alex J Lennon

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.11.1405160846330.18243@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@yoctoproject.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.