All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Passing MACs to Linux
Date: Thu, 05 Jun 2008 11:31:27 -0400	[thread overview]
Message-ID: <484806CF.9080505@ge.com> (raw)
In-Reply-To: <E6746F4E58F84F74A00907F0ECE81BE8@absolutdaddy>

Russell McGuire wrote:
> Guys,
> 
> I am sure this has been brought up a number of times, so forgive me in 
> advance.
> 
> I did notice however, not sure which version, but between 1.3.1 and 
> 1.3.3 U-boot That my MAC for my Ethernet device was no longer being
> passed into linux, or perhaps over written by the blob.
> 
> So for a quick status check.
> 
> What is the current operation / priority of how MACs are passed into 
> Linux 2.6.24+ vs the U-boot 1.3.3+ environment string?

Check what your .dts source looks like vs. an example .dts of the same 
processor (and, preferably a similar/same board) from the linux source 
tree.  As you noticed, things have been improving in the 2.6.2x and 
1.3.x timeframes, but .dts improvements are necessary to support the 
code improvements.

I would especially look at your .dts and see if it has a /aliases node 
with properties that point to your CPU, serial, ethernet, (and other?) 
properties.  The newer fixup functions look up the generic name in 
/aliases and use that to find the "real" property to fix up rather than 
having lots of hardcoded board/cpu specific #defines compiled into 
u-boot to fix up the "real" property directly.

"All problems in computer science can be solved by another level of 
indirection." - Butler Lampson

HTH,
gvb

      parent reply	other threads:[~2008-06-05 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 14:49 [U-Boot-Users] Passing MACs to Linux Russell McGuire
2008-06-05 15:02 ` Wolfgang Denk
2008-06-05 15:59   ` Russell McGuire
2008-06-05 16:19     ` Jerry Van Baren
2008-07-09 21:54     ` Paul Gortmaker
2008-06-05 15:31 ` 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=484806CF.9080505@ge.com \
    --to=gerald.vanbaren@ge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.