From: Timur Tabi <timur@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: mac-address vs. local-mac-address
Date: Wed, 07 Feb 2007 16:16:44 -0600 [thread overview]
Message-ID: <45CA4FCC.1000706@freescale.com> (raw)
In-Reply-To: <1170886032.2620.309.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
>> Without a firmware device tree, there's no way to update the device tree and
>> have that new tree retained over a reboot.
>
> I don't think it was ever question to update it over reboot...
Well, it is a good idea to use the same MAC address at every boot. The question
becomes: when you change the MAC address in Linux, is it possible to retain that
value over reboot? If the driver were able to update the *real* OF tree, then
we could provide that functionality (on OF-enabled systems).
My main point was to define when mac-address should be used, and when
local-mac-address should be used.
> mac-address is a runtime property that is lost at reboot, at least
> that's my understanding of the OF behaviour. That's where your confusion
> is.
Linux already stores the current MAC address somewhere outside of the OF tree.
When I reboot the system, does Linux store the current MAC address somewhere?
--
Timur Tabi
Linux Kernel Developer @ Freescale
prev parent reply other threads:[~2007-02-07 22:16 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
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 [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=45CA4FCC.1000706@freescale.com \
--to=timur@freescale.com \
--cc=benh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).