From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 1/1] netbase: make netbase recipe MACHINE specific for all targets
Date: Fri, 03 Feb 2012 09:15:13 -0800 [thread overview]
Message-ID: <4F2C1621.2050401@linux.intel.com> (raw)
In-Reply-To: <4F2ADCF6.4030000@linux.intel.com>
On 02/02/2012 10:59 AM, Joshua Lock wrote:
> On 02/02/12 10:54, Koen Kooi wrote:
>>
>> Op 2 feb. 2012, om 19:51 heeft Joshua Lock het volgende
>> geschreven:
>>
>>> Several BSP's are appending netbase to add MACHINE specific
>>> networking functionality. Rather than BSP creators having to
>>> mark netbase MACHINE specific just default to PACKAGE_ARCH =
>>> "${MACHINE_ARCH}" in netbase.
>>>
>>> This shouldn't be a huge hit as netbase just copies files
>>> around.
>>
>> In the past OE would mark things machine specific if something in
>> SRC_URI was fetched using overrides. So it this patches fixed
>> netbase the 'old' mechanism is broken :(
>
> This patch doesn't fix netbase, I just thought it would be simpler to
> make this change than ensure all BSP's use appropriate OVERRIDEs in
> their netbase bbappends - several I've seen don't.
>
Is there a consensus on whether or not this can go in? I need either
this or the BSP layer fix for a new BSP. It seems to me that netbase is
overridden enough for machine specific things (like the interface file)
that Joshua's approach is the better fix.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-02-03 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 18:51 [PATCH 0/1] Force netbase to be MACHINE specific for all MACHINEs Joshua Lock
2012-02-02 18:51 ` [PATCH 1/1] netbase: make netbase recipe MACHINE specific for all targets Joshua Lock
2012-02-02 18:54 ` Koen Kooi
2012-02-02 18:59 ` Joshua Lock
2012-02-03 17:15 ` Darren Hart [this message]
2012-02-04 16:07 ` Koen Kooi
2012-02-06 18:33 ` Joshua Lock
2012-02-06 18:58 ` Koen Kooi
2012-02-06 19:37 ` Joshua Lock
2012-02-06 19:50 ` Koen Kooi
2012-02-06 19:55 ` Joshua Lock
2012-02-03 21:07 ` Khem Raj
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=4F2C1621.2050401@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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 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.