public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Enabling smc911x driver
Date: Tue, 21 Apr 2009 09:32:38 -0700	[thread overview]
Message-ID: <49EDF526.9060709@gmail.com> (raw)
In-Reply-To: <5e088bd90904210811j2bf9fe7ep922fb1564389445e@mail.gmail.com>

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

  reply	other threads:[~2009-04-21 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 15:11 [U-Boot] Enabling smc911x driver Steve Sakoman
2009-04-21 16:32 ` Ben Warren [this message]
2009-04-22 14:52   ` Steve Sakoman
2009-04-22 15:51     ` Daniel Mack
2009-04-22 15:54       ` Daniel Mack
2009-04-22 17:31         ` Steve Sakoman
2009-04-22 18:08           ` Daniel Mack
2009-04-23  4:20           ` Steve Sakoman
2009-04-23  6:43             ` Daniel Mack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49EDF526.9060709@gmail.com \
    --to=biggerbadderben@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox