[meta-freescale] [3rdparty PATCH 0/4] Allow easier use of mainline-based BSP on i.MX products (Nitrogen6x support)

[Otavio Salvador]

On Sat, Mar 25, 2017 at 3:03 PM, Gary Bisson
<gary.bisson at boundarydevices.com> wrote:
> First of all, thank you for this series and the great job you've done to
> add mainline support, this is highly appreciated!

This was indeed an important step. It makes easier to compare both BSP
support now.

> On Fri, Mar 24, 2017 at 05:12:12PM -0300, Otavio Salvador wrote:
>>
>> This patchset makes use of the infrastructure added to meta-freescale
>> to enable easier use of mainline-based BSP. To enable it, include:
>>
>> MACHINEOVERRIDES .= ":use-mainline-bsp"
>>
>> To the local.conf and everything is done automatically.
>>
>> The bootscript still needs some love to work out of box but this will
>> be left for Boundary Devices ;-)
>
> I've fixed one of the two issues already [1] so bootdir doesn't need to
> be set any more.

Great.

> The only thing that still needs to be figured out is the root= parameter
> which right now requires the following variable to be set when booting a
> Nitrogen6X with WiFi module from first SD slot:
> => setenv root /dev/mmcblk1p2
>
> The reason is that mainline kernel doesn't allow to change the numbering
> order of SDHC devices based on aliases. Sascha offered a patch which
> never got accepted (but is in the NXP tree) [2].
>
> So on a device where a WiFi module is present, the first sdcard device
> will be named mmcblk1. But on a SabreLite (no WiFi), it will be mmcblk0
> as the bootscript thinks it is.
>
> I haven't found a good approach yet to fix it, ideas are welcomed ;)

Use UUID for booting. It can be done on U-Boot as it can pass the UUID
for the root= argument. See:

https://github.com/Freescale/u-boot-fslc/commit/b4227954508ac995e9ded35ea055456788a2e807

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750