[meta-freescale] u-boot for i.mx6Q doesn't initialize usdhc4

[Wally Yeh]

>>This is on purpose; the U-Boot code is board specific so you need to
>>make a board configuration and initialization (on the board file)
>>according to your board layout.

Thanks, I will create a recipe for what I wanna modify.

I found I have make a mistake: uboot  in yocto(version v2014.01-r0)
initialize usdhc2~4, and skip usdhc1. not usdhc4.

so my device had change it's number from "mmc dev 3" to "mmc dev 2".

Wally


2014-09-07 2:15 GMT+08:00 Otavio Salvador <otavio at ossystems.com.br>:

> On Sat, Sep 6, 2014 at 1:39 PM, Wally Yeh <wally.yeh at atrustcorp.com>
> wrote:
> > Dear All:
> >     hello, I have a custom board for i.mx6Q, it have almost the same
> layout
> > with mx6q_sabresd board. this board attach one eMMC on it's usdhc4
> port(so
> > It will locate in mmc dev 3 in uboot).
> >
> >     Since I change uboot form SDK_3.0.35 to yocto. my board can't
> recognize
> > mmc dev 3 anymore.
> >
> >     I notice uboot  in yocto(version v2014.01-r0) just initialize
> usdhc1~3,
> > and skip usdhc4.
> >
> >     Does this is a design on purpose or an issue need to fix?
>
> This is on purpose; the U-Boot code is board specific so you need to
> make a board configuration and initialization (on the board file)
> according to your board layout.
>
> --
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20140907/f43413c0/attachment.html>