All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ann Thornton <Ann.Thornton@freescale.com>
To: <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm] mesa-demos broken on nitrogen6x
Date: Mon, 17 Aug 2015 15:37:05 -0500	[thread overview]
Message-ID: <55D245F1.9090805@freescale.com> (raw)
In-Reply-To: <CADseiPm+upfxAaeRpm=6DrPK-zq5uo1gdbRaW3GXwo+pnk=ryA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]


The reason it doesn't just use _mx6 is that is doesn't apply to _mx6ul.

I don't think it is valid to have a machine that is both mx6dl and mx6q.

Ann Thornton

On 8/17/2015 2:29 PM, Ian Coolidge wrote:
> meta-fsl-arm/recipes-graphics/mesa/mesa-demos_%.bbappend has the 
> following lines of code:
>
> # only apply patches on mx6 that have a GPU
> SRC_URI_append_mx6q  = " ${MESA-DEMO-PATCH}"
> SRC_URI_append_mx6dl = " ${MESA-DEMO-PATCH}"
> SRC_URI_append_mx6sx = " ${MESA-DEMO-PATCH}"
> SRC_URI_append_mx6sl = " ${MESA-DEMO-PATCH}"
>
> And meta-fsl-arm-extra/conf/machine/nitrogen6x.conf declares its 
> SOC_FAMILY as:
>
> SOC_FAMILY = "mx6:mx6dl:mx6q"
>
> This causes the MESA-DEMO-PATCH to be applied twice as the nitrogen6x 
> is both mx6dl and mx6q since we have many CPU models of the nitrogen6x.
>
> Is there any reason the recipe couldn't just have:
>
> SRC_URI_append_mx6 = " ${MESA-DEMO-PATCH}"
>
> Thanks for the help!
>
>


-- 
Ann Thornton

/Microcontrollers Software and Applications
Freescale Semiconductors
email: Ann.Thornton@freescale.com/

[-- Attachment #2: Type: text/html, Size: 2693 bytes --]

  parent reply	other threads:[~2015-08-17 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 19:29 [meta-fsl-arm] mesa-demos broken on nitrogen6x Ian Coolidge
2015-08-17 20:03 ` Doug Schwanke
2015-08-17 20:37 ` Ann Thornton [this message]
2015-08-17 21:43   ` Fabio Estevam
2015-08-18  0:00     ` Otavio Salvador
2015-08-18  0:26       ` Ian Coolidge
2015-08-18 10:02         ` Otavio Salvador

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=55D245F1.9090805@freescale.com \
    --to=ann.thornton@freescale.com \
    --cc=meta-freescale@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.