From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 1/3] zaurusd: enable support for collie
Date: Mon, 05 Sep 2011 09:53:29 +0100 [thread overview]
Message-ID: <1315212810.14490.25.camel@rex> (raw)
In-Reply-To: <CALT56yOh6E9=51CWv9r-6Qz62wycn7MC4sn5pCKPEQziE07-QA@mail.gmail.com>
On Sat, 2011-09-03 at 23:04 +0400, Dmitry Eremin-Solenikov wrote:
> On 9/3/11, Koen Kooi <koen@dominion.thruhere.net> wrote:
> > shouldn't this move to meta-zaurus now that oe-core is qemu only?
>
> Maybe. IIUC, currently the plan is to push meta-zaurus into meta-hh as published
> by Paul Eggleton. On the other hand we didn't start this move (yet).
> So please ignore
> this patch for now.
>
> BTW: Probably this patch and fix-makefile.patch should just be applied
> into main git?
We should apply these patches straight into git, yes.
I'm also wondering if there is still a use case for renaming zaurusd and
turning it into something less machine specific (which was always its
intent).
One place it can really help is where you have several revisions of a
board and need a slightly different audio config for each as it allows
doing this with one OE 'machine' entry.
Cheers,
Richard
prev parent reply other threads:[~2011-09-05 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-03 18:22 [PATCH 1/3] zaurusd: enable support for collie Dmitry Eremin-Solenikov
2011-09-03 18:22 ` [PATCH 2/3] icu-3.6: fix building with big make -j Dmitry Eremin-Solenikov
2011-09-05 19:39 ` Richard Purdie
2011-09-03 18:22 ` [PATCH 3/3] qt-demo-init: fix init script Dmitry Eremin-Solenikov
2011-09-05 19:38 ` Richard Purdie
2011-09-03 18:28 ` [PATCH 1/3] zaurusd: enable support for collie Koen Kooi
2011-09-03 19:04 ` Dmitry Eremin-Solenikov
2011-09-05 8:53 ` Richard Purdie [this message]
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=1315212810.14490.25.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox