public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mvgbe: remove setting of ethaddr within the driver
Date: Thu, 10 Nov 2011 17:30:13 +0100	[thread overview]
Message-ID: <4EBBFC15.9050107@keymile.com> (raw)
In-Reply-To: <20111110155311.66DB613BE0E2@gemini.denx.de>

On 11/10/2011 04:53 PM, Wolfgang Denk wrote:
> In message <20111110142152.GC29864@kw.sim.vm.gnt> you wrote:
>>
>> I suspect a lot of Marvell boards from being in the same case.
> 
> Argh... I was not aware that the scope of damage already done was that
> big.
> 

On the Keymile boards (for marvell boards, km_kirkwood) we have an EEPROM that
stores the ethaddr for each board, so we should not be affected by the removal
of this "feature" (the driver setting ethaddr).

Cheers

Valentin

  reply	other threads:[~2011-11-10 16:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 22:08 [U-Boot] [PATCH] mvgbe: remove setting of ethaddr within the driver Michael Walle
2011-11-08  7:18 ` Prafulla Wadaskar
2011-11-08 13:58   ` Mike Frysinger
2011-11-08 14:10     ` Wolfgang Denk
2011-11-08 13:57 ` Mike Frysinger
2011-11-08 13:45   ` Michael Walle
2011-11-08 14:54     ` Mike Frysinger
2011-11-08 15:17     ` Wolfgang Denk
2011-11-08 17:34       ` Michael Walle
2011-11-08 19:28         ` Wolfgang Denk
2011-11-08 22:30           ` Michael Walle
2011-11-08 22:52             ` Wolfgang Denk
2011-11-08 23:26               ` Michael Walle
2011-11-08 23:38                 ` Wolfgang Denk
2011-11-09  8:31                 ` Michael Walle
2011-11-09 17:34                   ` Michael Walle
2011-11-09 19:27                     ` Wolfgang Denk
2011-11-10  9:15                       ` Michael Walle
2011-11-10 11:06                         ` Simon Guinot
2011-11-10 12:01                           ` Wolfgang Denk
2011-11-10 14:21                             ` Simon Guinot
2011-11-10 15:53                               ` Wolfgang Denk
2011-11-10 16:30                                 ` Valentin Longchamp [this message]
2011-11-10 17:00                                   ` Holger Brunck
2011-11-10 17:08                                   ` Mike Frysinger
2011-11-10 17:09                               ` Mike Frysinger
2011-11-10 17:54                                 ` Simon Guinot
2011-11-10 17:46                               ` Michael Walle
2011-11-10 11:44                         ` Wolfgang Denk
2011-11-16 20:15                           ` Michael Walle
2011-11-16 20:26                             ` Wolfgang Denk
2011-11-17  8:58                               ` Prafulla Wadaskar
2011-11-17 10:45                                 ` Wolfgang Denk
2011-11-17 22:52                                 ` [U-Boot] [PATCH v2] " Michael Walle
2011-11-19  3:58                                   ` Mike Frysinger
2011-11-21  4:39                                   ` Prafulla Wadaskar
2011-12-20 21:55                                   ` Wolfgang Denk
2011-12-20 21:57                                   ` Wolfgang Denk
2011-11-08 20:49         ` [U-Boot] [PATCH] " Mike Frysinger
2011-11-08 22:45           ` Michael Walle
2011-11-09  5:36             ` Mike Frysinger

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=4EBBFC15.9050107@keymile.com \
    --to=valentin.longchamp@keymile.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox