Hi Wolfgang, On Tue, January 3, 2012 09:09, Wolfgang Denk wrote: >> > 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?
The linkstations don't have a (populated) serial port. There is no way to access an unmodified board other than using the netconsole. If you want to recover from a bad environment setting or an empty environment, you can do this only with a working network connection. -- michael _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
