I don't think it needs to be there. Doing a 'mac' init is all that I would think need be done. It doesn't have the big delay of the phy init but gets rid of u-boot to kernel handshake issues, and also sets up the environment.

In board's I used in the past, I just did the mac init section in misc_init_r and not a full ethinit.

Regards,

Richard W.

-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users- admin@lists.sourceforge.net] On Behalf Of Paul Ruhland Sent: Thursday, June 10, 2004 2:59 PM To: u-boot-users@lists.sourceforge.net Subject: [U-Boot-Users] lib_arm/board.c calls eth_init() for smc91111...why?

I noticed when my board booted with the latest CVS there was an

unusually

long delay (3-4 seconds) before the prompt came up. I initially thought it

had

hung. Turns out a call to 'eth_init()' was recently added in 'lib_arm/board.c'. Since 'eth_init()' is called from 'Net_Loop()' why

do

we need the call in board.c? It adds quite a large delay to the bootup

time

that I think is unnecessary.

-- Paul Ruhland pruhland@microwavedata.com Software Engineer Microwave Data Systems Rochester, NY 16420

---

This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users