All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Eric Ruei <e-ruei1@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH V2 1/2] conf/layer.conf: Build omapdrm-pvr only if SGX is included
Date: Thu, 3 Dec 2015 13:19:36 -0500	[thread overview]
Message-ID: <20151203181935.GS6264@edge> (raw)
In-Reply-To: <1448984390-21457-2-git-send-email-e-ruei1@ti.com>

On Tue, Dec 01, 2015 at 10:39:49AM -0500, Eric Ruei wrote:
> Enable non-SGX build for AM3/AM4:
> Build SGX DDK kernel module (omapdrm-pvr.ko) only if SGX is not
> included at MACHINE_FEATURES.
> 
> Signed-off-by: Eric Ruei <a0850410@uda0850410>

^^^^ Still problems with gitconfig?


> ---
>  conf/layer.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/conf/layer.conf b/conf/layer.conf
> index 51da372..f471e72 100644
> --- a/conf/layer.conf
> +++ b/conf/layer.conf
> @@ -11,7 +11,7 @@ BBFILE_PRIORITY_meta-ti = "6"
>  LICENSE_PATH += "${LAYERDIR}/licenses"
>  
>  SIGGEN_EXCLUDERECIPES_ABISAFE += " \
> -    omapdrm-pvr \
> +    ${@base_contains('MACHINE_FEATURES', 'sgx', 'omapdrm-pvr', ' ', d)} \

You don't really need to do this.


>      omap5-sgx-ddk-um-linux \
>      ti-ipc \
>      cmem-mod \
> -- 
> 1.9.1
> 
> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti


  reply	other threads:[~2015-12-03 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 15:39 [PATCH V2 0/2] Enable non-SGX build for AM3/AM4 Eric Ruei
2015-12-01 15:39 ` [PATCH V2 1/2] conf/layer.conf: Build omapdrm-pvr only if SGX is included Eric Ruei
2015-12-03 18:19   ` Denys Dmytriyenko [this message]
2015-12-01 15:39 ` [PATCH V2 2/2] omap5-sgx-ddk-um-linux: Configure DDK UM based on the availability of SGX Eric Ruei
2015-12-03 18:21   ` Denys Dmytriyenko

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=20151203181935.GS6264@edge \
    --to=denys@ti.com \
    --cc=e-ruei1@ti.com \
    --cc=meta-ti@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.