Marc Leeman wrote:
>> I presume the problem is that the /aliases node doesn't exist in your
>> tree (original kernel .dts source, and thus the .dtb blob). One simple
>> solution would be to create the /aliases node if it doesn't exist, just
>> like we create the /chosen node if it doesn't exist.
>
> Yep, that's how I got to boot my kernel again, forgot to post this in my
> previous mail:
>
> aliases {
> ethernet0 = &enet0;
> ethernet1 = &enet1;
> serial0 = &serial0;
> serial1 = &serial1;
> pci0 = &pci0;
> };
>
> And then adding the correct aliases of course:
> enet0: [EMAIL PROTECTED] {
> etc.
Ahh, right. My thought of auto-creating the /aliases node is a very bad
idea. We could guess that ethernet0 is suppose to be mapped to &enet0,
but it would be a guess and there is a non-trivial probability of
guessing wrong. The whole *reason* for having an /aliases node is to
avoid guessing (and being wrong sometimes). The /aliases node really is
describing how the board is to be used, so it really needs to be defined
in the .dts source.
Best regards,
gvb
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
