From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] 1.3.2-rc2 83xx CONFIG_HAS_ETHX not passing MAC addresses
Date: Sat, 01 Mar 2008 18:11:36 -0500 [thread overview]
Message-ID: <47C9E2A8.2020102@gmail.com> (raw)
In-Reply-To: <20080301214525.GU16684@chiana.homelinux.org>
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: ethernet at 24000 {
> 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
prev parent reply other threads:[~2008-03-01 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 13:03 [U-Boot-Users] 1.3.2-rc2 83xx CONFIG_HAS_ETHX not passing MAC addresses Marc Leeman
2008-02-29 13:49 ` Marc Leeman
2008-02-29 16:07 ` Scott Wood
2008-03-01 11:06 ` Marc Leeman
2008-03-03 19:30 ` Scott Wood
2008-03-01 19:18 ` Jerry Van Baren
2008-03-01 21:45 ` Marc Leeman
2008-03-01 23:11 ` Jerry Van Baren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47C9E2A8.2020102@gmail.com \
--to=gvb.uboot@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox