2008/6/2 Wolfgang Denk wd@denx.de:

In message 5a65fa170806011449j5c3a480cta792c5d5ffeb58aa@mail.gmail.com you wrote:

...

I recently read the FAQ again and found about using valid MAC addresses:

• Should I recompile my u-boot with the new local-admin MAC address or just

I need to write the new config on the board?

Neither one nor the other. You just have to define a correct value for the "ethaddr" variable in your environment and save that.

Thanks. That's what I wanted to mean when I said writing config on the board. :)

2008/6/2 Ken.Fuchs@bench.com:

Victor (pfc) wrote:

...

I've been working last months on a lubbock board and u-boot as a bootloader to run Linux. I always loaded my kernel via serial port, because I never got u-boot to activate my ethernet (I never got the link led on, only after booting Linux).

...

I recently read the FAQ again and found about using valid MAC addresses:

...

• Should I recompile my u-boot with the new local-admin MAC address or just I need to write the new config on the board?

To change the MAC addresses, only the environment needs to change as follows ...

u-boot> setenv ethaddr <valid MAC address> (eth0) u-boot> setenv eth1addr <valid MAC address1> (eth1) u-boot> setenv eth2addr <valid MAC address2> (eth2) u-boot> saveenv

Omit references to eth1 or eth2, if they don't exist on your specific board.

There is no need to recompile U-Boot.

Sincerely,

Ken Fuchs

Thanks, did it. There's something I must been doing wrong, because I can't manage to get it work. The "link" led never turns on until I boot Linux. Then everythings works as it should. But uploading data to the board through a serial link is *slow*.