"Hong Xu" <[EMAIL PROTECTED]> wrote: > >> or something like this. I don't know if AT91_BASE_EMAC is visible > >> from this code, so you may need to modify slightly. > > Can we do a cpu_eth_init instead? > Not all arm926ejs series have built-in ethernet controller (e.g. > AT91SAM9261 does not have). If we do it in cpu_eth_init, we may need > other more #ifdef_s to distinguish. :-)
In _my_ opinion, I think it's much cleaner to just let the board code decide which and how many ethernet controllers to initialize instead of having some #ifdef maze in the CPU code. But it's not may call. Oh, and another thing... > >> extern int macb_eth_initialize(int id, void *regs, unsigned int phy_addr); We're getting more and more of these. Does anyone know an appropriate header to put it in? Haavard ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
