All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@linux.intel.com>
To: Leon Woestenberg <leon.woestenberg@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/5] Fedora 14 Patches
Date: Thu, 09 Dec 2010 16:57:38 +0000	[thread overview]
Message-ID: <1291913858.1554.909.camel@rex> (raw)
In-Reply-To: <AANLkTikvUb+SmGvn3i=U7KpEiYHq24XbOnjZMFTh6K1j@mail.gmail.com>

On Thu, 2010-12-09 at 16:43 +0100, Leon Woestenberg wrote:
> Is something preventing the Yocto guys to look at the OpenEmbedded
> GIT, where these machines and recipes came from in the first place?

No, this is something we do a lot of the time and you can see it in the
commit logs. When something comes from OE, credit is given.

> Obviously most of these machines come directly from OE.
> 
> What I don't understand is that all that is sitting in OpenEmbedded is
> considered 'new' in Poky/Yocto, while it was thrown away in the first
> place by Poky and Yocto.

Nothing has ever been thrown away. Poky has been around a long time,
things get added to OE which didn't make it into Poky. What Joshua is
trying to understand is what missing.

> We have had numerous discussion on how we can extend Yocto back to
> include the PowerPC, ARM, MIPS stuff again, but it takes people to
> look across the wall again.

qemuppc, qemuarm and qemumips built and boot in Poky, we test this
extremely regularly so there is no fundamental architecture issue. Where
did this come from? Large chunks of it from OE. There is obviously some
problem for certain classes of machines. I'd very much like to
understand what is broken so we can go and fix it.

> If there's legal issues involved in looking over the wall, I'ld like
> to see that confirmed, as it greatly influences the way we can work
> with the community.

There are no legal issues.

Cheers,

Richard



  reply	other threads:[~2010-12-09 16:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 21:13 [PATCH 0/5] Fedora 14 Patches Wolfgang Denk
2010-12-07 21:13 ` [PATCH 1/5] eglibc: fix build issue with make-3.82 Wolfgang Denk
2010-12-07 21:14 ` [PATCH 2/5] gstreamer: " Wolfgang Denk
2010-12-07 21:14 ` [PATCH 3/5] Add support for 40x configuration (kilauea from OE) Wolfgang Denk
2010-12-07 21:14 ` [PATCH 4/5] elfutils-0.148: fix build problem with "ar" Wolfgang Denk
2010-12-07 21:14 ` [PATCH 5/5] elfutils-0.148: fix problems with `ld' not recognizing options Wolfgang Denk
2010-12-07 22:01 ` [PATCH 0/5] Fedora 14 Patches Wolfgang Denk
2010-12-08 11:24 ` Paul Eggleton
2010-12-08 11:35   ` Wolfgang Denk
2010-12-08 22:18     ` Saul Wold
2010-12-09  8:58       ` Wolfgang Denk
2010-12-09 12:30         ` Joshua Lock
2010-12-09 15:43           ` Leon Woestenberg
2010-12-09 16:57             ` Richard Purdie [this message]
2010-12-09 16:06           ` Wolfgang Denk
2010-12-09 18:46             ` Joshua Lock
2010-12-09 22:01               ` Wolfgang Denk
2010-12-09 17:29           ` Wolfgang Denk
2010-12-09 18:40             ` Joshua Lock
2010-12-09 19:58               ` Wolfgang Denk
2010-12-09 19:25         ` Saul Wold
2010-12-08 16:39   ` Wolfgang Denk

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=1291913858.1554.909.camel@rex \
    --to=rpurdie@linux.intel.com \
    --cc=leon.woestenberg@gmail.com \
    --cc=poky@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.