From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mvgbe: remove setting of ethaddr within the driver
Date: Wed, 16 Nov 2011 21:15:33 +0100 [thread overview]
Message-ID: <201111162115.33330.michael@walle.cc> (raw)
In-Reply-To: <20111110114426.E5B4C13BE0E2@gemini.denx.de>
Hi Wolfgang,
Am Donnerstag 10 November 2011, 12:44:26 schrieb Wolfgang Denk:
> Dear Prafulla,
>
> In message <48935aa530a6457b76b9915a1fe7faf9.squirrel@ssl.serverraum.org>
Michael Walle wrote:
> > >> So was there any conclusion, now? Never touch mvgbe.c anymore?
> > >
> > > Let's remove this broken code.
> >
> > This is exactly part of this patch ([PATCH] mvgbe: remove setting of
> > ethaddr within the driver). This part, while ACK'ed by Mike, was NAK'ed
> > by Prafulla.
>
> Could you please revise your assessment? I would really appreciate if
> we could clean this up.
Regarding Prafulla's NAK?
Let me sum up this thread once again:
- consens is found that the driver should be cleaned up (removing the
randomization code)
- at least the keymile boards are ok with that. but there may be plenty of
other boards which rely on this (broken?) behaviour.
- besides the fact that a driver must not touch the environment, the mvgbe
driver also fails to do this correctly for boards which has only the second
port enabled.
- Prafulla NAKed because only removing the code will leave some boards in a
non-working state.
i'm willing make a patch to move the randomization functionality to some
generic place, but only if it is not NAKed by you beforehand. i dont have any
time to waste ;)
--
Michael
next prev parent reply other threads:[~2011-11-16 20:15 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
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 [this message]
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=201111162115.33330.michael@walle.cc \
--to=michael@walle.cc \
--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.