[meta-freescale] [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Eric Nelson]

On 10/16/2013 10:04 AM, Otavio Salvador wrote:
> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
> <eric.nelson at boundarydevices.com> wrote:
>> Hi Otavio,
>>
>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>
>>> The SabreLITE machine is now supported using the Boundary Devices
>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>> overrides of this recipe.
>>>
>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>> Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>
>>> ---
>>>    .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>>    .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>>> --------------------
>>>    recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>>    3 files changed, 7748 deletions(-)
>>>    delete mode 100644
>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>>    delete mode 100644
>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>>
>>
>> It seems that this broke something. Machine-type "imx6qsabrelite" will
>> fail to fetch because of a missing defconfig file.
>>
>> With MACHINE="imx6qsabrelite", the fetch command for "linux-boundary"
>> doesn't know to search in "nitrogen6x/" as shown below.
>>
>> Is there a way to fix this besides copying the directory?
>
> Yes; you can add it to the MACHINEOVERRIDES.
>
> You can add to imx6qsabrelite.conf:
>
> MACHINEOVERRIDES =. "nitrogen6x"
>
> This should do the trick.
>
Thanks Otavio.

I had to use "=" instead of "=." or the fetch process would look
in a directory named "nitrogen6ximx6qsabrelite/".

A patch is forthcoming.