On Mon, 29 Oct 2007 12:45:54 +0100 "Ulf Samuelsson" ulf@atmel.com wrote:
Also: I am not proposing a "default" address just that the user can, by running a command, set the ethaddr to something which is useful for production. If the user does not run the command, then the address will remain unset. Once the ethaddr is set to a different value, it should, as usual, not be possible to change it.
Oh. But why are you opposed to this change which simply removes the default address? You can still use setenv to set ethaddr to anything you want.
I am not opposed to the change, I just point out that there is a use for an initial ethernet address and an initial ip address.
I want to be able to download linux/root fs without connecting to a serial port at all. To provide a setenv command, I then have to put it in the bootcmd. I do want to avoid having a 1 kB+ large bootcmd, which would be required if you want to set up the environment this way.
The proposed method will allow the board to reset to a known state easily, something which is not possible if you program the environment or program the board using setenv command.
The bootcmd, would, using the proposed method, run the command to define the environment, and then download an autoscript which would define the rest of the environment. There is no need for a serial communication which may, or may not be availbable.
It all boils downto, that some people prefer a certain way and others prefer to do it in a different way. I believe in letting the customer decide his method.
It is important, to solve the problem with duplicate ethernet addresses.
Best Regards Ulf Samuelsson ulf@atmel.com