Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Sat, 2011-04-16 at 06:31 +0200, Koen Kooi wrote:
> 
> Op 15 apr. 2011 om 20:26 heeft Saul Wold <sgw@linux.intel.com> het volgende geschreven:
> 
> > On 04/15/2011 10:00 AM, Paul Eggleton wrote:
> >> From: Paul Eggleton<paul.eggleton@linux.intel.com>
> >> 
> >> Avoids manual configuration of the BeagleBoard xM's ethernet port (which
> >> shows up as usb0).
> >> 
> >> Fixes [YOCTO #930]
> >> 
> >> Signed-off-by: Paul Eggleton<paul.eggleton@linux.intel.com>
> >> ---
> >>  .../netbase/netbase-4.45/beagleboard/interfaces    |   27 ++++++++++++++++++++
> >>  1 files changed, 27 insertions(+), 0 deletions(-)
> >>  create mode 100644 meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces
> >> 
> > I know this time would come!
> > 
> > So this is up for discussion in a big way!
> > 
> > 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.
> 
> 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.

Cheers,

Richard