From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ben Warren <biggerbadderben@gmail.com>
Date: Tue, 21 Apr 2009 09:32:38 -0700
Subject: [U-Boot] Enabling smc911x driver
In-Reply-To: <5e088bd90904210811j2bf9fe7ep922fb1564389445e@mail.gmail.com>
References: <5e088bd90904210811j2bf9fe7ep922fb1564389445e@mail.gmail.com>
Message-ID: <49EDF526.9060709@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Steve,

Steve Sakoman wrote:
> I'm attempting to enable the smc911x driver for the overo omap3 board.
>
> Looking at the README and a couple of board config files, it seems
> that defining CONFIG_DRIVER_SMC911X,  CONFIG_DRIVER_SMC911X_16_BIT (or
> 32_BIT), and CONFIG_DRIVER_SMC911X_BASE is all that is required.  I
> have also enabled CONFIG_CMD_NET, CONFIG_CMD_DHCP and CONFIG_CMD_PING.
>
> The build completes successfully, but it seems that the driver init is
> never called, so I assume I am missing something.
>
> Do I need to add an explicit init call to my board or cpu file?  At
> first glance I don't see that other boards are doing this.
>
>   
This driver uses the old-style API and so requires board/cpu init code 
to call eth_init().  I'm not familiar with your architecture, so don't 
know how or if this is implemented, but it should be easy to find 
another example that does this.
> Thanks!
>
> Steve
> ________
regards,
Ben