From: Saul Wold <sgw@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: poky@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Date: Fri, 15 Apr 2011 11:26:43 -0700 [thread overview]
Message-ID: <4DA88DE3.2050702@linux.intel.com> (raw)
In-Reply-To: <72ccbf03bcbec48a34d830c356e591a9139e3794.1302886579.git.paul.eggleton@linux.intel.com>
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.
I believe and others will have to confirm this, that some distros may
want to use these core files, but not via meta-yocto as a layer, or do
those distros have these files modified differently (ie, not just
copies, which would be bad).
This is all food for thought.
Sau!
> diff --git a/meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces b/meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces
> new file mode 100644
> index 0000000..b6935c1
> --- /dev/null
> +++ b/meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces
> @@ -0,0 +1,27 @@
> +# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
> +
> +# The loopback interface
> +auto lo
> +iface lo inet loopback
> +
> +# Wireless interfaces
> +iface wlan0 inet dhcp
> + wireless_mode managed
> + wireless_essid any
> + wpa-driver wext
> + wpa-conf /etc/wpa_supplicant.conf
> +
> +iface atml0 inet dhcp
> +
> +# Wired or wireless interfaces
> +auto eth0
> +iface eth0 inet dhcp
> +iface eth1 inet dhcp
> +
> +# Ethernet/RNDIS gadget (g_ether) or LAN9514 on BeagleBoard xM
> +auto usb0
> +iface usb0 inet dhcp
> +
> +# Bluetooth networking
> +iface bnep0 inet dhcp
> +
next prev parent reply other threads:[~2011-04-15 18:29 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 ` Saul Wold [this message]
2011-04-16 4:31 ` [poky] " 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
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=4DA88DE3.2050702@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox