From: Joe Hamman <joe.hamman@embeddedspecialties.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Device tree and u-boot passing MAC addressquestions
Date: Mon, 17 Dec 2007 14:37:16 -0600 [thread overview]
Message-ID: <006001c840ec$9cf09090$7100a8c0@ESIDT> (raw)
In-Reply-To: <4766DC57.6080708@ge.com>
> -----Original Message-----
> From: Jerry Van Baren [mailto:gerald.vanbaren at ge.com]
> Sent: Monday, December 17, 2007 2:30 PM
> To: joe.hamman at embeddedspecialties.com
> Cc: 'robert lazarski'; 'U-Boot-Users'
> Subject: Re: [U-Boot-Users] Device tree and u-boot passing MAC
> addressquestions
>
> Joe Hamman wrote:
> > Hi Robert,
> >
> > [snip]
> >
> >> To get eth2 to link, I put this MAC in my device tree:
> >>
> >> local-mac-address = [ 00 E0 0C 00 02 FD ];
> >>
> >> Otherwise the kernel just sees a series of zero's . Is this change on
> >> purpose and I missed what I need to do now?
> >>
> >
> > I recently encountered the same problem. By using the 'fdt b' command,
> I
> ^
> "fdt p" I presume. |
Sorry, I should have listed all the steps:
tftp 10000 filename.dtb # load the dtb
fdt a 10000 # tell fdt where it loaded
fdt b # do the board specific setup (fills
in MAC)
fdt p # verify the values are correct
>
> > was able to see that the MAC addresses were not being filled in prior to
> > calling the kernel.
> >
> > Adding aliases to the dtb file fixed my problem. (Search the mailing
> > lists...)
> >
> > Best regards,
> > Joe
next prev parent reply other threads:[~2007-12-17 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 17:56 [U-Boot-Users] Device tree and u-boot passing MAC address questions robert lazarski
2007-12-17 18:37 ` Timur Tabi
2007-12-17 18:47 ` robert lazarski
2007-12-17 20:27 ` [U-Boot-Users] Device tree and u-boot passing MAC addressquestions Joe Hamman
2007-12-17 20:30 ` Jerry Van Baren
2007-12-17 20:37 ` Joe Hamman [this message]
2007-12-17 20:56 ` Timur Tabi
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='006001c840ec$9cf09090$7100a8c0@ESIDT' \
--to=joe.hamman@embeddedspecialties.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