All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] mips: When booting Linux images, add'ethaddr' and 'eth1addr' to the environment
Date: Tue, 08 Jul 2008 22:55:56 +0900	[thread overview]
Message-ID: <487371EC.4040003@ruby.dti.ne.jp> (raw)
In-Reply-To: <1215438409.31842.61.camel@mcmullan-linux.cifs.lab.netapp.com>

McMullan, Jason wrote:
> On Sun, 2008-07-06 at 14:59 +0900, Shinya Kuribayashi wrote:
>> Jason McMullan wrote:
>>> Add 'ethaddr' and 'eth1addr' to the Linux kernel environment if
>>> they are set in the U-Boot environment.
>> Looking closely into linux/arch/*, I found that mips is the only
>> architecture which supports the 'ethaddr' kernel parameter.  Is this
>> right?  What I want to make sure is whether 'ethaddr' is an unusual
>> kernel parameter or not.
> 
> On our devices, the U-Boot environment is the only place the ethernet
> MAC address is stored.
> 
> Since the infrastructure for passing environment variables up to the
> MIPS Linux kernel existed anyways, I decided that it would be a better
> plan to use that machanism than to have the kernel dig through the
> duplicate U-Boot environments.

Thanks for the explanations.  As Linux/MIPS kernel supports this
parameter anyway, it's good for U-Boot to support that, too.

Applied, will send to Wolfgang asap.


  Shinya

      reply	other threads:[~2008-07-08 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09  3:56 [U-Boot-Users] [PATCH] mips: When booting Linux images, add 'ethaddr' and 'eth1addr' to the environment Jason McMullan
2008-07-06  5:59 ` Shinya Kuribayashi
2008-07-07 13:46   ` [U-Boot-Users] [PATCH] mips: When booting Linux images, add'ethaddr' " McMullan, Jason
2008-07-08 13:55     ` Shinya Kuribayashi [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=487371EC.4040003@ruby.dti.ne.jp \
    --to=skuribay@ruby.dti.ne.jp \
    --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.