In message [off-list ref] you wrote:
...
come out. We think that is because linux is thinking the MAC address is
ff:ff:ff:ff:ff:ff instead of what
it really is. u-boot doesn't seem to have a problem getting the MAC
address out of the ebony board, but
this linux kernel seems to.
U-Boot passes the MAC address to the Linux kernel, so if your kernel
is configured for use with U-Boot, then it will pick up the correct
MAC address. Maybe it is not?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
No one may kill a man. Not for any purpose. It cannot be condoned.
-- Kirk, "Spock's Brain", stardate 5431.6
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Is there something special that must be done for the kernel to be
configured for use
with u-boot? A kernel config option, perhaps?
I double checked the include/asm-ppc/u-boot.h in u-boot against
include/asm-ppc/ppcboot.h in linux...and
did find a section with a #define for CONFIG_405, but not 440. We'll see
if that makes a difference.
At 07:59 PM 5/19/04 +0200, Wolfgang Denk wrote:
In message [off-list ref]
you wrote:
quoted
...
quoted
come out. We think that is because linux is thinking the MAC address is
ff:ff:ff:ff:ff:ff instead of what
it really is. u-boot doesn't seem to have a problem getting the MAC
address out of the ebony board, but
this linux kernel seems to.
U-Boot passes the MAC address to the Linux kernel, so if your kernel
is configured for use with U-Boot, then it will pick up the correct
MAC address. Maybe it is not?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
No one may kill a man. Not for any purpose. It cannot be condoned.
-- Kirk, "Spock's Brain", stardate 5431.6
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/