public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] what's the uboot way to pass eth*addr to linux ?
Date: Sat, 20 Feb 2010 16:08:45 +0100	[thread overview]
Message-ID: <20100220150845.F2BD5E3A67D@gemini.denx.de> (raw)
In-Reply-To: <20100220093717.GA9602@frolo.macqel>

Dear Philippe De Muyter,

In message <20100220093717.GA9602@frolo.macqel> you wrote:
>
> Previously, the mac addresses were stored in the bd_info struct, but that
> has been removed, but alas not replaced by a common mechanism for all
> architectures.

Complain about this to the Linux architecture maintainers - there have
been many and longf discussions about this before.

Today we consider the device tree to be the Right Thing (TM) to pass
such information to the kernel, and more and more architectures use
this method.

As long as it's not available for your architecture, the most
straightforward way is to pass an "ethaddr=..." argument on the
kernel command line. Drivers can pick it up easily there. Just don't
expect that such Linux driver code will be accepted for mainline.

  reply	other threads:[~2010-02-20 15:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 17:50 [U-Boot] what's the uboot way to pass eth*addr to linux ? Philippe De Muyter
2010-02-20  7:30 ` Maxim Podbereznyi
2010-02-20  9:37   ` Philippe De Muyter
2010-02-20 15:08     ` Wolfgang Denk [this message]
2010-02-20 23:59       ` Philippe De Muyter
2010-02-21 16:29         ` Wolfgang Denk
2010-03-05 19:32     ` Mike Frysinger
2010-02-20 10:38   ` Philippe De Muyter
2010-02-20 14:49     ` Maxim Podbereznyi
2010-02-21  0:47       ` Philippe De Muyter
2010-02-21  4:07         ` Ben Warren
2010-02-21 16:25         ` Wolfgang Denk

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=20100220150845.F2BD5E3A67D@gemini.denx.de \
    --to=wd@denx.de \
    --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