All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Joshua Lock <josh@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [pull-sys940x 4/4] netbase: Add interfaces with RANDOM_MAC for sys940x* machines
Date: Thu, 02 Feb 2012 10:31:44 -0800	[thread overview]
Message-ID: <4F2AD690.5000900@linux.intel.com> (raw)
In-Reply-To: <4F29C4DF.50704@linux.intel.com>



On 02/01/2012 03:03 PM, Joshua Lock wrote:
> 
> 
> On 01/02/12 14:52, Joshua Lock wrote:
>>> +++ b/meta-sys940x/recipes-core/netbase/netbase_4.47.bbappend
>>> @@ -0,0 +1,3 @@
>>> +FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>>> +RDEPENDS_${PN} += "genmac"
>>
>> We can use a MACHINE specific override here, I think.
>>
>> RDEPENDS_${PN}_sys940x += "genmac"
>>
>> Ideally we don't want that interfaces file on non-sys940x machines,
>> perhaps we could name the interfaces file differently and add a
>> do_install_append_sys940x which installs the MACHINE specific interface
>> file?
> 
> In this instance, however, I don't know what would happen if we built 
> netbase with this layer enabled for a different core2 MACHINE and then 
> built for the sys940x....
> 
> I suspect the existing core2 package would be used and think for this 
> approach to work we'd need to mark this recipe MACHINE specific.
> 
> Cheers,
> Joshua

Thanks for catching this. As I understand it, Richard and Joshua have
agreed that netbase should just be MACHINE specific. Joshua has agreed
to prep a patch to this effect, rendering this recipe OK as is.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2012-02-02 18:32 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 22:26 [pull-sys940x 0/4][meta-intel] Inforce SYS940X BSP (Intel Atom E6xx + EG20T) Darren Hart
2012-02-01 22:26 ` [pull-sys940x 1/4] meta-intel: Add Inforce SYS940x BSP Darren Hart
2012-02-01 22:37   ` Joshua Lock
2012-02-01 23:05     ` Joshua Lock
2012-02-02 18:07       ` Darren Hart
2012-02-01 22:26 ` [pull-sys940x 2/4] ranpwd: Add ranpwd recipe Darren Hart
2012-02-01 22:40   ` Joshua Lock
2012-02-02  7:22     ` Martin Jansa
2012-02-02 18:26       ` Darren Hart
2012-02-02 19:13         ` Joshua Lock
2012-02-02 19:34           ` Darren Hart
2012-02-02 18:24     ` Darren Hart
2012-02-02 19:24       ` Joshua Lock
2012-02-02 19:32         ` Darren Hart
2012-02-02 21:11           ` Joshua Lock
2012-02-06 16:17             ` Paul Eggleton
2012-02-06 23:59               ` Joshua Lock
2012-02-07  7:06                 ` Martin Jansa
2012-02-07  9:20                   ` [yocto] " Koen Kooi
2012-02-11  0:14                   ` Darren Hart
2012-02-11  1:45                     ` Khem Raj
2012-02-01 22:26 ` [pull-sys940x 3/4] genmac: Replace RANDOM_MAC in network/interfaces with a randomly generated MAC Darren Hart
2012-02-01 22:42   ` Joshua Lock
2012-02-02 18:27     ` Darren Hart
2012-02-02 14:09   ` William Mills
2012-02-02 17:19     ` Darren Hart
2012-02-02 18:37       ` William Mills
2012-02-01 22:26 ` [pull-sys940x 4/4] netbase: Add interfaces with RANDOM_MAC for sys940x* machines Darren Hart
2012-02-01 22:52   ` Joshua Lock
2012-02-01 23:03     ` Joshua Lock
2012-02-02 18:31       ` Darren Hart [this message]
2012-02-02 19:02       ` Joshua Lock

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=4F2AD690.5000900@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=josh@linux.intel.com \
    --cc=yocto@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 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.