public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NET: SDP3430: trouble with shifting from LAN9C916 to SMC91XX driver
Date: Wed, 14 Oct 2009 07:56:57 -0500	[thread overview]
Message-ID: <4AD5CA99.5080305@ti.com> (raw)
In-Reply-To: <f8328f7c0910132136p409df4d2ge21c499398187051@mail.gmail.com>

Ben Warren had written, on 10/13/2009 11:36 PM, the following:
> Nishanth,
> 
> On Tue, Oct 13, 2009 at 8:13 PM, Nishanth Menon <nm@ti.com 
> <mailto:nm@ti.com>> wrote:
> 
>     Hi Folks,
> 
>     While attempting to address the warning for SDP3430 as pointed out by
>     dirk in [1], I did a patch corresponding to what was done for EVM(353x)
>     as in [2]. unfortunately, this wont work for me, I get:
>     U-Boot 2009.08-00515-gfea6a55-dirty (Oct 12 2009 - 14:03:23)
> 
>     OMAP3530-GP ES3.0, CPU-OPP2 L3-165MHz
>     OMAP3 SDP3430 board + LPDDR/NOR
>     I2C:   ready
>     DRAM:  128 MB
>     Flash: 128 MB
>     In:    serial
>     Out:   serial
>     Err:   serial
>     smc911x: Invalid chip endian 0xdee0013d
>     Net:   No ethernet found.
>     OMAP34XX SDP #
> 
>     and no network, using LEGACY driver seems to be working just great
>     for me.
> 
>     Note: in my patch [2], I did try both CONFIG_SMC911X_32_BIT and
>     CONFIG_SMC911X_16_BIT with no luck either way.  I even tried to hack the
>     driver by skipping the supported chip detection code, but the driver
>     still did not work for me.
> 
> When using CONFIG_NET_MULTI you need to have a board_eth_init() function 
done
> in your board code which in turn must call smc911x_initialize().  Make 
done
> sure that eth_initialize() gets called somewhere in your cpu/board.c 
why eth_initalize? rest of the OMAP3 boards dont seem to be doing that
> call sequence.  I suspect that while the SMC911x driver is being 
> initialized, it isn't being registered properly with the networking 
> library.  There are many examples in the source tree of how to do this.
I would expect that and did check too, but why:
smc911x: Invalid chip endian 0xdee0013d
when I had a base address and device which was supported by LAN91C96 
legacy driver?

My lack of network chip knowledge is kicking me at the moment.. trying 
to find the device data sheet internally @ TI..

-- 
Regards,
Nishanth Menon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-TI-OMAP3-SDP3430-dont-use-legacy-ethernet-driver.patch
Type: text/x-patch
Size: 0 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20091014/0609a35a/attachment.bin 

  reply	other threads:[~2009-10-14 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14  3:13 [U-Boot] NET: SDP3430: trouble with shifting from LAN9C916 to SMC91XX driver Nishanth Menon
2009-10-14  4:36 ` Ben Warren
2009-10-14 12:56   ` Nishanth Menon [this message]
2009-10-14 19:00     ` Ben Warren
2009-10-15  1:46       ` Nishanth Menon
2009-10-15  5:05         ` Ben Warren
2009-10-15  6:05           ` Menon, Nishanth

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=4AD5CA99.5080305@ti.com \
    --to=nm@ti.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