From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Date: Mon, 18 Apr 2011 10:53:10 +0100 [thread overview]
Message-ID: <1303120390.5518.88.camel@rex> (raw)
In-Reply-To: <E3CCB8FD-559F-4700-B922-FC7C86033E40@dominion.thruhere.net>
On Mon, 2011-04-18 at 11:30 +0200, Koen Kooi wrote:
> Op 18 apr 2011, om 11:17 heeft Paul Eggleton het volgende geschreven:
>
> > 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
>
> You mean meta-texasinstruments, right? Or do you yocto folks keep
> going to deny that there's an upstream layer for beagleboard support?
To quote my email from earlier today:
"""
> It should live in the upstream beagleboard BSP layer, which currently
> is meta-texasinstruments
That is the goal, yes. It was agreed that until we sort out the layer
tooling, there would be some code in meta-yocto which would be a copy of
various upstream parts which includes beagleboard. Over time I'm hoping
to see these pieces converge, then we when get the tooling right it will
become automated.
"""
which I'd hardly call denial. There is a plan indicated above which we
agreed to and we intend to follow unless there is a problem?
Cheers,
Richard
next prev parent reply other threads:[~2011-04-18 9:55 UTC|newest]
Thread overview: 18+ 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-16 4:31 ` Koen Kooi
2011-04-18 7:05 ` Richard Purdie
2011-04-18 9:17 ` Paul Eggleton
2011-04-18 9:30 ` Koen Kooi
2011-04-18 9:53 ` Richard Purdie [this message]
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:43 ` Gary Thomas
2011-04-15 23:01 ` Darren Hart
2011-04-18 9:12 ` Paul Eggleton
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=1303120390.5518.88.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox