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 14:18:23 -0500 [thread overview]
Message-ID: <47C9ABFF.8080105@gmail.com> (raw)
In-Reply-To: <20080229130318.GR16684@chiana.homelinux.org>
Marc Leeman wrote:
> When booting an 8347 processor, the MAC addresses (ethaddr and eth1addr)
> don't seem to get passed anymore.
>
> I modified my config to include CONFIG_HAS_ETH0 and CONFIG_HAS_ETH1 and
> I am entering the code in fdt_fixup_ethernet (common/fdt_support.c) but
> get stuck at node = fdt_path_offset(fdt, "/aliases");
>
> Once this fails, the MAC addresses are not passed along.
Disclaimer: I have not researched this...
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.
Best regards,
gvb
next prev parent reply other threads:[~2008-03-01 19:18 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 [this message]
2008-03-01 21:45 ` Marc Leeman
2008-03-01 23:11 ` Jerry Van Baren
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=47C9ABFF.8080105@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