From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Frysinger Date: Thu, 10 Nov 2011 12:08:16 -0500 Subject: [U-Boot] [PATCH] mvgbe: remove setting of ethaddr within the driver In-Reply-To: <4EBBFC15.9050107@keymile.com> References: <1320703689-4879-1-git-send-email-michael@walle.cc> <20111110155311.66DB613BE0E2@gemini.denx.de> <4EBBFC15.9050107@keymile.com> Message-ID: <201111101208.17858.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thursday 10 November 2011 11:30:13 Valentin Longchamp wrote: > 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). curious, but is it an eeprom on an external bus, or is it connected to the mvgbe block ? -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20111110/f3f92d08/attachment.pgp