/etc/network/interfaces updates
cover /etc/network/interfaces updates
From: Paul Eggleton <[email protected]>
Some fixes for /etc/network/interfaces.
Pull URL: git://git.openembedded.org/openembedded-core-contrib
Branch: paule/netbase-fixes
Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/netbase-fixes
Thanks,
Paul Eggleton <[email protected]>
---
Paul Eggleton (3):
netbase: automatically bring up eth0
netbase: automatically bring up usb0 on beagleboard
netbase: add /etc/network/interfaces file for qemumips & qemuppc
.../netbase/netbase-4.45/beagleboard/interfaces | 27 ++++++++++++++++++++ meta/recipes-core/netbase/netbase-4.45/interfaces | 1 + .../netbase/netbase-4.45/qemumips/interfaces | 8 ++++++ .../netbase/netbase-4.45/qemuppc/interfaces | 8 ++++++ 4 files changed, 44 insertions(+), 0 deletions(-) create mode 100644 meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces create mode 100644 meta/recipes-core/netbase/netbase-4.45/qemumips/interfaces create mode 100644 meta/recipes-core/netbase/netbase-4.45/qemuppc/interfaces
PATCH 1/3 netbase: automatically bring up eth0
From: Paul Eggleton <[email protected]>
This avoids manual configuration for those machines that do not override the default /etc/network/interfaces file.
Fixes [YOCTO #875]
--- meta/recipes-core/netbase/netbase-4.45/interfaces | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
meta/recipes-core/netbase/netbase-4.45/interfaces +1 -0
@@ -14,6 +14,7 @@ iface wlan0 inet dhcp iface atml0 inet dhcp # Wired or wireless interfaces +auto eth0 iface eth0 inet dhcp iface eth1 inet dhcp
Signature · 1 line
1.7.1
PATCH 2/3 netbase: automatically bring up usb0 on beagleboard
In reply to Paul EggletonFrom: Paul Eggleton <[email protected]>
Avoids manual configuration of the BeagleBoard xM's ethernet port (which shows up as usb0).
Fixes [YOCTO #930]
--- .../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
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +27 -0
@@ -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 +
Signature · 1 line
1.7.1
PATCH 3/3 netbase: add /etc/network/interfaces file for qemumips & qemuppc
In reply to Paul EggletonFrom: Paul Eggleton <[email protected]>
This fixes the network configuration for qemumips & qemuppc to match the other qemu* machines.
--- .../netbase/netbase-4.45/qemumips/interfaces | 8 ++++++++ .../netbase/netbase-4.45/qemuppc/interfaces | 8 ++++++++ 2 files changed, 16 insertions(+), 0 deletions(-) create mode 100644 meta/recipes-core/netbase/netbase-4.45/qemumips/interfaces create mode 100644 meta/recipes-core/netbase/netbase-4.45/qemuppc/interfaces
meta/recipes-core/netbase/netbase-4.45/qemumips/interfaces new file +8 -0
@@ -0,0 +1,8 @@ +# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) + +# The loopback interface +auto lo +iface lo inet loopback + + +
meta/recipes-core/netbase/netbase-4.45/qemuppc/interfaces new file +8 -0
@@ -0,0 +1,8 @@ +# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) + +# The loopback interface +auto lo +iface lo inet loopback + + +
Signature · 1 line
1.7.1
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
In reply to Paul EggletonQuoted 5 lines · Paul Eggleton
From: Paul Eggleton<[email protected]>
Avoids manual configuration of the BeagleBoard xM's ethernet port (which shows up as usb0).
Quoted 8 lines
Fixes [YOCTO #930]
Signed-off-by Paul Eggleton<[email protected]>--- .../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!
Quoted 33 lines
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +27
-0@@ -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 +
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
In reply to Paul EggletonQuoted 28 lines · Paul Eggleton
From: Paul Eggleton <[email protected]>
Avoids manual configuration of the BeagleBoard xM's ethernet port (which shows up as usb0).
Fixes [YOCTO #930]
Signed-off-by Paul Eggleton <[email protected]>--- .../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/interfacesmeta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +9
-0@@ -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
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces line 19
Quoted 10 lines
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +10
-0+ 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
Since we're adding a this specifically for the beagleboard, I don't see the value of adding eth0 or eth1. I'm not sure about wifi and bluetooth, I believe there are modules out there.
I suppose it doesn't hurt to have them there as examples.
Quoted 8 lines
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +8
-0+ +# Ethernet/RNDIS gadget (g_ether) or LAN9514 on BeagleBoard xM +auto usb0 +iface usb0 inet dhcp + +# Bluetooth networking +iface bnep0 inet dhcp +
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Quoted 37 lines · Darren Hart
Quoted 34 lines · Paul Eggleton
From: Paul Eggleton<[email protected]>
Avoids manual configuration of the BeagleBoard xM's ethernet port (which shows up as usb0).
Fixes [YOCTO #930]
Signed-off-by Paul Eggleton<[email protected]>--- .../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
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +15
-0@@ -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 +
Quoted 8 lines
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces line 19
Quoted 4 lines
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +4
-0+# Wired or wireless interfaces +auto eth0 +iface eth0 inet dhcp +iface eth1 inet dhcpSince we're adding a this specifically for the beagleboard, I don't see the value of adding eth0 or eth1. I'm not sure about wifi and bluetooth, I believe there are modules out there.
eth1 yes, but doesn't the BeagleBoard xM have eth0?
Quoted 12 lines
I suppose it doesn't hurt to have them there as examples.
Quoted 8 lines
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +8
-0+ +# Ethernet/RNDIS gadget (g_ether) or LAN9514 on BeagleBoard xM +auto usb0 +iface usb0 inet dhcp + +# Bluetooth networking +iface bnep0 inet dhcp +
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Quoted 47 lines · Gary Thomas
Quoted 37 lines · Darren Hart
Quoted 34 lines · Paul Eggleton
From: Paul Eggleton<[email protected]>
Avoids manual configuration of the BeagleBoard xM's ethernet port (which shows up as usb0).
Fixes [YOCTO #930]
Signed-off-by Paul Eggleton<[email protected]>--- .../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
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +15
-0@@ -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 +Quoted 8 lines
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces line 19
Quoted 4 lines
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +4
-0+# Wired or wireless interfaces +auto eth0 +iface eth0 inet dhcp +iface eth1 inet dhcpSince we're adding a this specifically for the beagleboard, I don't see the value of adding eth0 or eth1. I'm not sure about wifi and bluetooth, I believe there are modules out there.
Quoted 1 line
eth1 yes, but doesn't the BeagleBoard xM have eth0?
No. The onboard device is usb0.
--
Darren
Quoted 14 lines
Quoted 13 lines
I suppose it doesn't hurt to have them there as examples.
Quoted 8 lines
meta/recipes-core/netbase/netbase-4.45/beagleboard/interfaces new file +8
-0+ +# Ethernet/RNDIS gadget (g_ether) or LAN9514 on BeagleBoard xM +auto usb0 +iface usb0 inet dhcp + +# Bluetooth networking +iface bnep0 inet dhcp +
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
In reply to Saul WoldOp 15 apr. 2011 om 20:26 heeft Saul Wold <[email protected]> het volgende geschreven:
Quoted 14 lines · Paul Eggleton
Quoted 5 lines
From: Paul Eggleton<[email protected]>
Avoids manual configuration of the BeagleBoard xM's ethernet port (which shows up as usb0).
Quoted 8 lines
Fixes [YOCTO #930]
Signed-off-by Paul Eggleton<[email protected]>--- .../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
Quoted 5 lines
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
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Quoted 30 lines · Koen Kooi
Op 15 apr. 2011 om 20:26 heeft Saul Wold <[email protected]> het volgende geschreven:
Quoted 14 lines · Paul Eggleton
Quoted 5 lines
From: Paul Eggleton<[email protected]>
Avoids manual configuration of the BeagleBoard xM's ethernet port (which shows up as usb0).
Quoted 8 lines
Fixes [YOCTO #930]
Signed-off-by Paul Eggleton<[email protected]>--- .../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/interfacesQuoted 5 lines
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.
Quoted 2 lines
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
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
In reply to Darren HartQuoted 4 lines · On Saturday 16 April 2011 00:01:30 Darren Hart wrote:
Quoted 1 line · Gary Thomas
eth1 yes, but doesn't the BeagleBoard xM have eth0?
No. The onboard device is usb0.
Looks like we're not the only ones confused by this:
https://bugs.launchpad.net/linux-linaro/+bug/622429
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre (UK)
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
In reply to Saul WoldQuoted 7 lines · 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
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Op 18 apr 2011, om 11:17 heeft Paul Eggleton het volgende geschreven:
Quoted 11 lines · On Friday 15 April 2011 19:26:43 Saul Wold wrote:
Quoted 7 lines
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? If so, that doesn't bode well for manufacturers wanting to support their boards that overlap with boards in meta-yocto.
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Quoted 11 lines · Koen Kooi
Op 18 apr 2011, om 11:17 heeft Paul Eggleton het volgende geschreven:
Quoted 9 lines · On Friday 15 April 2011 19:26:43 Saul Wold wrote:
Quoted 7 lines
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.
Quoted 5 lines
Quoted 2 lines
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:
"""
Quoted 2 lines
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
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Op 18 apr 2011, om 11:53 heeft Richard Purdie het volgende geschreven:
Quoted 31 lines · Koen Kooi
Quoted 11 lines
Op 18 apr 2011, om 11:17 heeft Paul Eggleton het volgende geschreven:
Quoted 9 lines · On Friday 15 April 2011 19:26:43 Saul Wold wrote:
Quoted 7 lines
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.
Quoted 5 lines
Quoted 2 lines
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:
"""
Quoted 2 lines
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.
"""
Quoted 2 lines
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?
This
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
I should
have pushed this particular patch to meta-yocto
bit from Pauls email indicates a problem. Since that is not pushing to upstream first (implied by the use of 'copy'), but keeping fixes only in the yocto layer.
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Quoted 36 lines · Koen Kooi
Op 18 apr 2011, om 11:53 heeft Richard Purdie het volgende geschreven:
Quoted 31 lines · Koen Kooi
Quoted 11 lines
Op 18 apr 2011, om 11:17 heeft Paul Eggleton het volgende geschreven:
Quoted 9 lines · On Friday 15 April 2011 19:26:43 Saul Wold wrote:
Quoted 7 lines
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.
Quoted 5 lines
Quoted 2 lines
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:
"""
Quoted 2 lines
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.
"""Quoted 2 lines
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?
Quoted 8 lines
This
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
I should
have pushed this particular patch to meta-yoctobit from Pauls email indicates a problem. Since that is not pushing to upstream first (implied by the use of 'copy'), but keeping fixes only in the yocto layer.
One step at a time. Getting pieces in roughly the right places is a good start, then we can look at syncing up any differences.
I can start jumping up and down every time someone duplicates something in meta-oe to be synced "later" if it would help? ;-)
I'd like to hope we can try and be a little less confrontational. A simple request asking "could you ensure this gets submitted to meta-texasinstruments" would have made things clear.
Cheers,
Richard
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
Op 18 apr 2011, om 13:04 heeft Richard Purdie het volgende geschreven:
Quoted 46 lines · Koen Kooi
Quoted 36 lines
Op 18 apr 2011, om 11:53 heeft Richard Purdie het volgende geschreven:
Quoted 31 lines · Koen Kooi
Quoted 11 lines
Op 18 apr 2011, om 11:17 heeft Paul Eggleton het volgende geschreven:
Quoted 9 lines · On Friday 15 April 2011 19:26:43 Saul Wold wrote:
Quoted 7 lines
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.
Quoted 5 lines
Quoted 2 lines
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:
"""
Quoted 2 lines
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.
"""Quoted 2 lines
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?
Quoted 8 lines
This
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
I should
have pushed this particular patch to meta-yoctobit from Pauls email indicates a problem. Since that is not pushing to upstream first (implied by the use of 'copy'), but keeping fixes only in the yocto layer.
Quoted 5 lines
One step at a time. Getting pieces in roughly the right places is a good start, then we can look at syncing up any differences.
I can start jumping up and down every time someone duplicates something in meta-oe to be synced "later" if it would help? ;-)
That would actually be very helpfull, there's too much crud in there that needs a cleanup. Which is slowly improving, though :)
regards,
Koen
Re: [poky] [PATCH 2/3] netbase: automatically bring up usb0 on beagleboard
In reply to Paul EggletonQuoted 10 lines · Paul Eggleton
Quoted 4 lines · On Saturday 16 April 2011 00:01:30 Darren Hart wrote:
Quoted 1 line · Gary Thomas
eth1 yes, but doesn't the BeagleBoard xM have eth0?
No. The onboard device is usb0.
Looks like we're not the only ones confused by this:
Perhaps I am missing some context, but I don't see any problem with having the name usb0. In fact, I find it informative, and helps to explain why things like tftp don't work from u-boot, etc.
While the community remains divided, I plan to stay in the usb0 camp.
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel