Dear Stefano Babic,
In message <4b62c655.3090...@denx.de> you wrote:
>
> I will add something like CONFIG_FSL_ESDHC_BIG_ENDIAN or
> CONFIG_FSL_ESDHC_LITTLE_ENDIAN in the driver I changed. In the related
> header file for the driver, I can set driver specific macros that point
> to the correct accessors, depending on the new CONFIG_ switch.
> Then it should be clear which is the endianess used and it will be not
> related to the processor architecture. What do you think about this ?
I like this approach better than the precious one.
However, I had hoped that we could do without such manual configu-
ration like CONFIG_FSL_ESDHC_*_ENDIAN. I mean, we already know the
target byte order, and you know in which byte order you want to
access the data, or is this board dependent?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
Anything that is worth doing at all is worth doing well.
-- Philip Earl of Chesterfield
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
