All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: yocto beagleboard.conf -- should it not go away?
Date: Mon, 03 Sep 2012 21:55:35 +0100	[thread overview]
Message-ID: <50451947.2090401@r-finger.com> (raw)
In-Reply-To: <CADkTA4NbPk6UDbctuj=McV1PT4QZu=2LRTq2-GHSAAoeaasAUw@mail.gmail.com>

Hi,

On 03/09/12 21:15, Bruce Ashfield wrote:
> On Mon, Sep 3, 2012 at 4:06 PM, Tomas Frydrych
> So we fix the configuration of the layers .. 

I expect this is not actually that trivial. I think the only way to do
this is properly is for the layer priorities to be respected by all
files in the layer, not just the bb files. No idea how involved that
change would be, or what the side effects would be.


> and meta-ti was supposed to work properly with meta-yocto last I heard.

If properly means 'out of the box', then no; the two layers can be made
to work together, but it's fairly clear that nobody comprehensively
tests that combination at the moment.


> The meta-yocto layer beagleboard configuration is a hardware ARM reference, that
> uses the linux-yocto kernel (policy and version) and is used for the
> project QA on hardware.

I am all for QA, but in this instance your QA procedure breaks things
for the end user. Could you not just call it something else, e.g.,
yocto-qa-arm-reference.conf?

Tomas


  reply	other threads:[~2012-09-03 20:55 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 [this message]
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
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=50451947.2090401@r-finger.com \
    --to=tf+lists.yocto@r-finger.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.