From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: poky@yoctoproject.org
Cc: "Wold, Saul" <saul.wold@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Date: Mon, 18 Apr 2011 10:17:59 +0100 [thread overview]
Message-ID: <201104181017.59589.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4DA88DE3.2050702@linux.intel.com>
On Friday 15 April 2011 19:26:43 Saul Wold wrote:
> There was some initial discussion at ELC this last week about what goes
> where and how layers are going to work moving forward. I know that we
> are committed to the qemu* machines in oe-core (meta), and that
> currently meta-yocto contains a set of core HW (beagleboard among them),
> so the question then is should the HW specific stuff, such as this patch
> move to meta-yocto or some other layer? There are a couple other
> recipes such as x-load and formfactor that contain HW specific files.
Ah, yes, you're right - we definitely don't want this file in oe-core. I should
have pushed this particular patch to meta-yocto (in support of the
basic/temporary beagleboard support we have there), so please ignore this one.
Cheers,
Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: poky@yoctoproject.org
Cc: "Wold, Saul" <saul.wold@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Date: Mon, 18 Apr 2011 10:17:59 +0100 [thread overview]
Message-ID: <201104181017.59589.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4DA88DE3.2050702@linux.intel.com>
On Friday 15 April 2011 19:26:43 Saul Wold wrote:
> There was some initial discussion at ELC this last week about what goes
> where and how layers are going to work moving forward. I know that we
> are committed to the qemu* machines in oe-core (meta), and that
> currently meta-yocto contains a set of core HW (beagleboard among them),
> so the question then is should the HW specific stuff, such as this patch
> move to meta-yocto or some other layer? There are a couple other
> recipes such as x-load and formfactor that contain HW specific files.
Ah, yes, you're right - we definitely don't want this file in oe-core. I should
have pushed this particular patch to meta-yocto (in support of the
basic/temporary beagleboard support we have there), so please ignore this one.
Cheers,
Paul
next prev parent reply other threads:[~2011-04-18 9:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 17:00 [PATCH 0/3] /etc/network/interfaces updates Paul Eggleton
2011-04-15 17:00 ` [PATCH 1/3] netbase: automatically bring up eth0 Paul Eggleton
2011-04-15 17:00 ` [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard Paul Eggleton
2011-04-15 18:26 ` [poky] " Saul Wold
2011-04-15 18:26 ` Saul Wold
2011-04-16 4:31 ` [poky] " Koen Kooi
2011-04-16 4:31 ` Koen Kooi
2011-04-18 7:05 ` [poky] " Richard Purdie
2011-04-18 7:05 ` Richard Purdie
2011-04-18 9:17 ` Paul Eggleton [this message]
2011-04-18 9:17 ` Paul Eggleton
2011-04-18 9:30 ` [poky] " Koen Kooi
2011-04-18 9:53 ` Richard Purdie
2011-04-18 10:48 ` Koen Kooi
2011-04-18 11:04 ` Richard Purdie
2011-04-18 11:17 ` Koen Kooi
2011-04-15 22:37 ` Darren Hart
2011-04-15 22:37 ` Darren Hart
2011-04-15 22:43 ` [poky] " Gary Thomas
2011-04-15 22:43 ` Gary Thomas
2011-04-15 23:01 ` [poky] " Darren Hart
2011-04-15 23:01 ` Darren Hart
2011-04-18 9:12 ` [poky] " Paul Eggleton
2011-04-18 9:12 ` Paul Eggleton
2011-04-18 16:07 ` [poky] " Darren Hart
2011-04-18 16:07 ` Darren Hart
2011-04-15 17:00 ` [PATCH 3/3] netbase: add /etc/network/interfaces file for qemumips & qemuppc Paul Eggleton
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=201104181017.59589.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--cc=saul.wold@intel.com \
/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.