From: William Mills <wmills@ti.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: yocto@yoctoproject.org, "Dmytriyenko, Denys" <denys@ti.com>
Subject: Re: yocto beagleboard.conf -- should it not go away?
Date: Wed, 5 Sep 2012 10:20:39 -0400 [thread overview]
Message-ID: <50475FB7.2080408@ti.com> (raw)
In-Reply-To: <50468D68.50608@linux.intel.com>
On 09/04/2012 07:23 PM, Darren Hart wrote:
>
>
> On 09/04/2012 01:25 PM, William Mills wrote:
>
>> Darren: Is it true you can't get @ the Intel BSP's w/o also getting the
>> poky distro defs? That does seem to mixing things a bit. (I am not
>> claiming meta-ti is clean yet but I want to understand the Intel examples.)
>>
>
> It isn't something we test as part of the QA that we perform. I mostly
> expect people building meta-intel to be building with meta-yocto
> (although I wouldn't take a hard line on requiring it). That said, I
> removed meta-yocto from a meta-intel/meta-fri2 build and removed
> DISTRO=poky from my local.conf and successfully built and booted a
> core-image-minimal build on an FRI2 this afternoon without any changes.
>
Thanks! My confidence is restored.
As long as including meta-yocto does not interfere with other BSPs or
distros etc then there should be no harm in your assumption.
I would be interested to know what Mentor Graphics and Wind River do on
their products. Do they include meta-yocto? (YP is not all about
comercial OS support but I know these orginatations have done the due
diligence on layer compatibility for a non-poky distro.)
next prev parent reply other threads:[~2012-09-05 14:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 20:06 yocto beagleboard.conf -- should it not go away? Tomas Frydrych
2012-09-03 20:15 ` Bruce Ashfield
2012-09-03 20:55 ` Tomas Frydrych
2012-09-03 21:08 ` Bruce Ashfield
2012-09-04 8:21 ` Jack Mitchell
2012-09-04 12:24 ` Bruce Ashfield
2012-09-05 22:03 ` Richard Purdie
2012-09-04 8:58 ` Tomas Frydrych
2012-09-04 12:20 ` Bruce Ashfield
2012-09-04 17:18 ` Darren Hart
2012-09-04 20:25 ` William Mills
2012-09-04 23:23 ` Darren Hart
2012-09-05 14:20 ` William Mills [this message]
2012-09-05 14:42 ` Darren Hart
2012-09-05 15:16 ` Bruce Ashfield
2012-09-05 21:52 ` Richard Purdie
2012-09-05 8:49 ` Tomas Frydrych
2012-09-05 9:15 ` Paul Eggleton
2012-09-05 9:43 ` Tomas Frydrych
2012-09-05 12:48 ` Richard Purdie
2012-09-05 14:45 ` William Mills
2012-09-05 15:06 ` Tomas Frydrych
2012-09-05 15:44 ` Richard Purdie
2012-09-05 19:34 ` Martin Jansa
2012-09-05 21:43 ` Richard Purdie
2012-09-05 14:39 ` Darren Hart
2012-09-08 7:18 ` Khem Raj
2012-09-05 21:46 ` Richard Purdie
2012-09-06 5:39 ` Tomas Frydrych
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=50475FB7.2080408@ti.com \
--to=wmills@ti.com \
--cc=denys@ti.com \
--cc=dvhart@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.