[meta-freescale] [meta-fsl-arm-extra][PATCH V2] linux-boundary: Add support for kernel 3.10.31_1.1.0_beta
eric.nelson at boundarydevices.com
Wed Nov 26 11:26:54 PST 2014
On 11/26/2014 11:10 AM, Gary Thomas wrote:
> On 2014-11-26 11:06, Gary Thomas wrote:
>> On 2014-11-23 18:57, Eric Nelson wrote:
>>> This patch adds support for the 3.10.31_1.1.0_beta kernelfor Boundary
>>> Devices BD-SL-i.MX6 (built to SABRE Lite), Nitrogen6X, Nitrogen6_Max
>>> and and Nitrogen6_Lite boards.
>>> To try it out, set PREFERRED_VERSION_linux-boundary = "3.10.31" in your
>>> local.conf file.
>>> Minimal testing has been performed at this point, so don't expect it
>>> to be production-ready.
>>> Note that the 3.10.31 kernel contains an update to provide fixed
>>> numbering for /dev/mmcblk devices instead of numbering them by
>>> order of initialization.
>>> Support has been added into the boot script, but requires setting
>>> a variable in U-Boot:
>>> U-Boot > setenv sdphys 1
>>> U-Boot > saveenv
>>> U-Boot > boot
>>> See this post for some additional commentary:
>>> Signed-off-by: Eric Nelson <eric.nelson at boundarydevices.com>
>> When I tried this patchset, it fails to boot my SabreLite. The
>> important bits seem to be the MMC device numbering. From the boot log:
>> mmc3: new high speed SDHC card at address aaaa
>> mmcblk3: mmc3:aaaa SU04G 3.69 GiB
>> mmcblk3: p1 p2
>> ALSA device list:
>> #0: imx6q-sabrelite-sgtl5000
>> Waiting for root device /dev/mmcblk0p2...
>> I see no difference when setting 'sdphys' or not. Perhaps I missed some
>> other patch (like to the boot scripts)?
> BTW, I'm building the scripts from
> and there seems to be nothing in there about sdphys
You need this patch to support the 'sdphys' thing in the boot script:
More information about the meta-freescale