Patchwork [meta-fsl-arm,1/2] imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra

login
register
mail settings
Submitter Otavio Salvador
Date April 6, 2013, 4:30 p.m.
Message ID <1365265828-28655-1-git-send-email-otavio@ossystems.com.br>
Download mbox | patch
Permalink /patch/47575/
State Accepted
Delegated to: Otavio Salvador
Headers show

Comments

Otavio Salvador - April 6, 2013, 4:30 p.m.
The SabreLITE is much better supported by Boundary kernel as being not
fully supported by Freescale new BSPs it should be moved to the Extra
layer where we can properly support it.

Change-Id: Ie6465c35a243cb199c3499eb4336c9638c9ce6ab
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
 conf/machine/imx6qsabrelite.conf | 16 ----------------
 1 file changed, 16 deletions(-)
 delete mode 100644 conf/machine/imx6qsabrelite.conf
Eric Nelson - April 6, 2013, 5:08 p.m.
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@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
>

Are there dependencies on this patch?

It didn't apply cleanly based on Master+patch 1 of the series.

Please advise,


Eric
Otavio Salvador - April 6, 2013, 5:13 p.m.
On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
<eric.nelson@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@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
>>
>
> Are there dependencies on this patch?
>
> It didn't apply cleanly based on Master+patch 1 of the series.

My tree looks like:

5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
680c6a3 gst-plugins-gl: Avoid leaking memory

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
Eric Nelson - April 6, 2013, 5:30 p.m.
On 04/06/2013 10:13 AM, Otavio Salvador wrote:
> On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
> <eric.nelson@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@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
>>>
>>
>> Are there dependencies on this patch?
>>
>> It didn't apply cleanly based on Master+patch 1 of the series.
>
> My tree looks like:
>
> 5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
> 1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
> 680c6a3 gst-plugins-gl: Avoid leaking memory
>
Thanks Otavio,

It looks like I had some leftover stuff in my local tree and
'repo init -b master' didn't fix it...
Otavio Salvador - April 6, 2013, 9:07 p.m.
On Sat, Apr 6, 2013 at 2:30 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 04/06/2013 10:13 AM, Otavio Salvador wrote:
>>
>> On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
>> <eric.nelson@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@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
>>>>
>>>
>>> Are there dependencies on this patch?
>>>
>>> It didn't apply cleanly based on Master+patch 1 of the series.
>>
>>
>> My tree looks like:
>>
>> 5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
>> 1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
>> 680c6a3 gst-plugins-gl: Avoid leaking memory
>>
> Thanks Otavio,
>
> It looks like I had some leftover stuff in my local tree and
> 'repo init -b master' didn't fix it...

You might use, next time:

repo sync
repo start test-otavio-patches --all

So it creates a new branch with current commited code.

Regards,

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
Eric Nelson - April 8, 2013, 3:01 p.m.
On 04/06/2013 02:07 PM, Otavio Salvador wrote:
> On Sat, Apr 6, 2013 at 2:30 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> On 04/06/2013 10:13 AM, Otavio Salvador wrote:
>>>
>>> On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
>>> <eric.nelson@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@ossystems.com.br>
>>>>> ---
>>>>
>>>> Are there dependencies on this patch?
>>>>
>>>> It didn't apply cleanly based on Master+patch 1 of the series.
>>>
>>> My tree looks like:
>>>
>>> 5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
>>> 1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
>>> 680c6a3 gst-plugins-gl: Avoid leaking memory
>>>
>> Thanks Otavio,
>>
>> It looks like I had some leftover stuff in my local tree and
>> 'repo init -b master' didn't fix it...
>
> You might use, next time:
>
> repo sync
> repo start test-otavio-patches --all
>
> So it creates a new branch with current commited code.
>

Thanks for the tip Otavio.

I've validated build success and that the kernel boots properly
with this series.

I'm not having success getting X to start up though.

Is the master branch known to have issues with DRM?

I'm seeing this in /var/log/Xsession.log:
	/usr/bin/Xorg: symbol lookup error: 
/usr/lib/xorg/modules/drivers/vivante_drv.so: undefined symbol: 
gcoHAL_MapUserMemory
Otavio Salvador - April 8, 2013, 4:04 p.m.
On Mon, Apr 8, 2013 at 12:01 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 04/06/2013 02:07 PM, Otavio Salvador wrote:
>>
>> On Sat, Apr 6, 2013 at 2:30 PM, Eric Nelson
>> <eric.nelson@boundarydevices.com> wrote:
>>>
>>> On 04/06/2013 10:13 AM, Otavio Salvador wrote:
>>>>
>>>>
>>>> On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
>>>> <eric.nelson@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@ossystems.com.br>
>>>>>> ---
>>>>>
>>>>>
>>>>> Are there dependencies on this patch?
>>>>>
>>>>> It didn't apply cleanly based on Master+patch 1 of the series.
>>>>
>>>>
>>>> My tree looks like:
>>>>
>>>> 5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
>>>> 1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
>>>> 680c6a3 gst-plugins-gl: Avoid leaking memory
>>>>
>>> Thanks Otavio,
>>>
>>> It looks like I had some leftover stuff in my local tree and
>>> 'repo init -b master' didn't fix it...
>>
>>
>> You might use, next time:
>>
>> repo sync
>> repo start test-otavio-patches --all
>>
>> So it creates a new branch with current commited code.
>>
>
> Thanks for the tip Otavio.

Great.

> I've validated build success and that the kernel boots properly
> with this series.

Good. I will apply this patch series.

> I'm not having success getting X to start up though.
>
> Is the master branch known to have issues with DRM?
>
> I'm seeing this in /var/log/Xsession.log:
>         /usr/bin/Xorg: symbol lookup error:
> /usr/lib/xorg/modules/drivers/vivante_drv.so: undefined symbol:
> gcoHAL_MapUserMemory

This does seem to be a regression and I will look at it later today.
Thanks for letting us know about it.

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
Eric Nelson - Oct. 16, 2013, 4:27 p.m.
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@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?


ERROR: Fetcher failure: Unable to find file file://defconfig anywhere. 
The paths that were searched were:
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/arm
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/armv7a
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/mx6
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/mx6q
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/imx6qsabrelite
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/poky
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/arm
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/armv7a
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/mx6
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/mx6q
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/imx6qsabrelite
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/poky
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/arm
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/armv7a
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/mx6
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/mx6q
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/imx6qsabrelite
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/poky
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/
     /home/ericn/yoctosl/downloads/
Otavio Salvador - Oct. 16, 2013, 5:04 p.m.
On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
<eric.nelson@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@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.
Eric Nelson - Oct. 16, 2013, 8:10 p.m.
On 10/16/2013 10:04 AM, Otavio Salvador wrote:
> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
> <eric.nelson@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@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.
Otavio Salvador - Oct. 16, 2013, 8:21 p.m.
On Wed, Oct 16, 2013 at 5:10 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 10/16/2013 10:04 AM, Otavio Salvador wrote:
>>
>> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
>> <eric.nelson@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@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.

MACHINEOVERRIDES =. "nitrogen6x:"

With the : it would work.
Eric Nelson - Oct. 16, 2013, 8:24 p.m.
On 10/16/2013 01:21 PM, Otavio Salvador wrote:
> On Wed, Oct 16, 2013 at 5:10 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> On 10/16/2013 10:04 AM, Otavio Salvador wrote:
>>>
>>> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
>>> <eric.nelson@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@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.
>
> MACHINEOVERRIDES =. "nitrogen6x:"
>
> With the : it would work.
>

Rats! I tried ":nitrogen6x" and got the same thing (nitrogen6ximx6q...).

Any problem with just = "nitrogen6x"?

Since we don't have a proper imx6qsabrelite directory, this seems
a reasonable approach.

Please advise,


Eric
Otavio Salvador - Oct. 16, 2013, 8:30 p.m.
On Wed, Oct 16, 2013 at 5:24 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 10/16/2013 01:21 PM, Otavio Salvador wrote:
>>
>> On Wed, Oct 16, 2013 at 5:10 PM, Eric Nelson
>> <eric.nelson@boundarydevices.com> wrote:
>>>
>>> On 10/16/2013 10:04 AM, Otavio Salvador wrote:
>>>>
>>>>
>>>> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
>>>> <eric.nelson@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@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.
>>
>>
>> MACHINEOVERRIDES =. "nitrogen6x:"
>>
>> With the : it would work.
>>
>
> Rats! I tried ":nitrogen6x" and got the same thing (nitrogen6ximx6q...).
>
> Any problem with just = "nitrogen6x"?
>
> Since we don't have a proper imx6qsabrelite directory, this seems
> a reasonable approach.

Yes but if we need a SABRELite dir in future we'll need to change it again.

It is up to you.
Eric Nelson - Oct. 16, 2013, 8:50 p.m.
On 10/16/2013 01:30 PM, Otavio Salvador wrote:
> On Wed, Oct 16, 2013 at 5:24 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> On 10/16/2013 01:21 PM, Otavio Salvador wrote:
>>>
>>> On Wed, Oct 16, 2013 at 5:10 PM, Eric Nelson
>>> <eric.nelson@boundarydevices.com> wrote:
>>>>
>>>> On 10/16/2013 10:04 AM, Otavio Salvador wrote:
>>>>>
>>>>>
>>>>> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
>>>>> <eric.nelson@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@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.
>>>
>>>
>>> MACHINEOVERRIDES =. "nitrogen6x:"
>>>
>>> With the : it would work.
>>>
>>
>> Rats! I tried ":nitrogen6x" and got the same thing (nitrogen6ximx6q...).
>>
>> Any problem with just = "nitrogen6x"?
>>
>> Since we don't have a proper imx6qsabrelite directory, this seems
>> a reasonable approach.
>
> Yes but if we need a SABRELite dir in future we'll need to change it again.
>

I hope we don't. The kernel takes care of all of that, and we should
be moving to consolidate via DT.

> It is up to you.
>

My preference is to use the patch as given and move forward.

Right now, the "imx6qsabrelite" machine type is simply broken.

Regards,


Eric

Patch

diff --git a/conf/machine/imx6qsabrelite.conf b/conf/machine/imx6qsabrelite.conf
deleted file mode 100644
index 6a0cef9..0000000
--- a/conf/machine/imx6qsabrelite.conf
+++ /dev/null
@@ -1,16 +0,0 @@ 
-#@TYPE: Machine
-#@NAME: i.MX6Q SABRE Lite
-#@DESCRIPTION: Machine configuration for Freescale i.MX6Q SABRE Lite
-
-include conf/machine/include/imx-base.inc
-include conf/machine/include/tune-cortexa9.inc
-
-SOC_FAMILY = "mx6q:mx6"
-
-KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx6q-sabrelite.dts"
-
-UBOOT_MACHINE = "mx6qsabrelite_config"
-
-SERIAL_CONSOLE = "115200 ttymxc1"
-
-MACHINE_FEATURES += " pci wifi bluetooth"