All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: mac-address vs. local-mac-address
Date: Wed, 07 Feb 2007 16:07:56 -0600	[thread overview]
Message-ID: <45CA4DBC.7090401@freescale.com> (raw)
In-Reply-To: <0EF1DDFB-E590-422C-8FA6-0FD643E68F49@kernel.crashing.org>

Kumar Gala wrote:

> The problem with u-boot is that the correct way would be to use 
> local-mac-address for what's compiled into u-boot and mac-address if 
> someone does a 'setenv' to modify the mac address.  The question is 
> anyone really going to care that much.

I don't think the compiled-in MAC address should be used at all.

For most boards, the compiled-in option is just some random MAC address.  When 
the board is shipped, the manufacturer creates his own set of environment 
variables and overrides what's stored on flash.

I actually think that storing a MAC address in a board configuration for or a 
DTS is a bad idea, because MAC addresses are supposed to be unique for each 
Ethernet device, and storing a fixed value in a source file breaks that. 
However, that's a separate issue.  I was just trying to stress that the 
compiled-in MAC address is of no value.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-02-07 22:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 21:17 mac-address vs. local-mac-address Timur Tabi
2007-02-07 21:32 ` Benjamin Herrenschmidt
2007-02-07 21:41   ` Kumar Gala
2007-02-07 21:46     ` Timur Tabi
2007-02-07 21:42   ` Timur Tabi
2007-02-07 21:51     ` Kumar Gala
2007-02-07 22:07       ` Timur Tabi [this message]
2007-02-07 22:14         ` Kumar Gala
2007-02-07 22:22           ` Timur Tabi
2007-02-07 22:07     ` Benjamin Herrenschmidt
2007-02-07 22:16       ` 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=45CA4DBC.7090401@freescale.com \
    --to=timur@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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.