[U-Boot-Users] [PATCH] update-ethaddr-handling-on-cmc-pu2-board.patch
Martin Krause
Martin.Krause at tqs.de
Wed Nov 16 13:55:05 CET 2005
Hi Pantelis,
Pantelis Antoniou wrote on Wednesday, November 16, 2005 1:19 PM:
> Martin Krause wrote:
> > If the environment variable 'ethaddr' is not set in flash it is
> > read from EEPROM (if valid), set in RAM and now also saved to
> > flash. The same applies for the variable 'serial#'. This is done to
> > optimise series production. Now, no 'saveenv' command
> > has to be applied over the serial line. And thus no serial
> > connection
> > is necessery at all. Setting ethaddr only in RAM is not sufficient,
> > because 'ethaddr' and 'serial#' must be readable from linux with
> > the fw_printenv tool.
>
> I disagree. If you need this, pass the u-boot environment to the linux
> kernel, or add a serial# member in bd_t.
I'm also not very happy with this. 'ethaddr' is already passed to the
linux kernel as boot parameter. But I didn' have access to it from
user space. Our customer (which buys the CMC-PU2 board from us), runs
an application which collects some board information from the u-boot
environemt variables stored in flash (via a /dev/mtd device). I can't
see, how a modified bd_t could help in this case.
Regards,
Martin
More information about the U-Boot
mailing list