[U-Boot] [PATCH] lsxl: add support for lschlv2 and lsxhl

Wolfgang Denk
2012-01-03T08:09:40Z

Dear Michael,

In message <201201030132.02862.michael@walle.cc> you wrote:
>
> > If Buffalo is the vendor, then why do you add this to the Marvell
> > vendor directory?
> I was just guessing. It is a Marvell SoC and marvell SoC boards of other
> vendors are in the Marvell/ directory, too. But i'm also happy with Buffalo/
> (or buffalo/?).

board/buffalo/, please.

> > NAK. We do not allow such static network configurations.
> i've already guessed that ;) you may remember our lengthy discussions about
> the board which don't have a dedicated NVRAM for the ethernet address. Well,
> this is such a board. I would have expected more responses from other
> maintainers of this type of boards, esp. after the patch which removes the mac
> randomization from the ethernet driver, was merged.

Actuaklly this is the standard case. Only a tiny minority of boards
provide such storage for the MAC address. The overwhelming majority
has none, and just uses the environment.

> So if
> #define CONFIG_ETHADDR xxx
> #define CONFIG_OVERWRITE_ETHADDR_ONCE
> is a no-no (i really dont see the point, why it's not allowed, sorry), i guess
> i have to maintain this on my own tree :(

It is not allowed because a MAC address is a _unique_ identifier.

Can you explain why you think it is needed at all? There are probably
some 900+ board configurations which don't need it (only in mainline,
not counting any out-of-tree ports), so why do you need it?

Best regards,

Wolfgang Denk

--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A wise person makes his own decisions, a weak one obeys public
opinion. -- Chinese proverb