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