[meta-freescale] imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Gunnar Roth]

>> But i have no clue why i have to change all this (mmcroot and fdt_file) in uboot, when i build an image for this very sabresd board.
>> Is the other setting beneficial for anyone using this board?

>The mmcroot issue was fixed in master; so please update and confirm it
>works for you.

Hmm i built on top of 
2014-07-28 12:16 Otavio Salvador    o [HEAD] [m/master] [yocto/master] u-boot-fslc: Update to 7a3b1da revision
which says
main] 6ef8db67df3436a463851ff95dcfb6a66132f3c0 - commit 1 of 1196 (0%)
commit 6ef8db67df3436a463851ff95dcfb6a66132f3c0
Refs: HEAD, <m/master>, <yocto/master>, 1.6-34-g6ef8db6
Author:     Otavio Salvador <otavio at ossystems.com.br>
AuthorDate: Mon Jul 28 12:16:42 2014 -0300
Commit:     Otavio Salvador <otavio at ossystems.com.br>
CommitDate: Mon Jul 28 12:16:42 2014 -0300

    u-boot-fslc: Update to 7a3b1da revision

    This includes the following changes:

    7a3b1da mx6sabresd: Use mmcblk0 for CONFIG_MMCROOT



So i would assume them  mmcblk0 issue should be fixed in my build. I read about that change here and made an update and bitbaked again.
But it is not yet working for me.

>The fdt_file is indeed a bug and we're after the root cause of it as
>the 2014.07 version of U-Boot includes the PMIC support.

so this is about powermanagment device volatage regulator and we want to use device tree without ldo? well i have only a very very small knowledge of this stuff.
But would it be possible to set back in git to the ldo ftd as long as imx6q-sabresd.dtb does not work? That was a really bad linux experience for me.

Best regards,
Gunnar