From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Warren Date: Wed, 14 Oct 2009 22:05:49 -0700 Subject: [U-Boot] NET: SDP3430: trouble with shifting from LAN9C916 to SMC91XX driver In-Reply-To: <782515bb0910141846w57ea7b0fvd6f1fe7734b0ae7d@mail.gmail.com> References: <4AD541CF.3000505@ti.com> <4AD5CA99.5080305@ti.com> <4AD61FDF.8020001@gmail.com> <782515bb0910141846w57ea7b0fvd6f1fe7734b0ae7d@mail.gmail.com> Message-ID: <4AD6ADAD.7030204@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Nishanth Menon wrote: > On Wed, Oct 14, 2009 at 2:00 PM, Ben Warren wrote: > [...] > >> The SMC911x chips all contain the magic value 0x87654321 @ offset 0x64. >> Your board has something else there (it's obviously not an endianness >> issue, so ignore the error message text). I think you need to learn >> more about your board, in particular which SMCS chip you're using, which >> data width and where it's located in memory. This is a simple >> memory-mapped device, and once you find out where it's located, it >> should 'just work' >> >> Here's a datasheet for reference. See page 68 for the memory map. >> >> http://www.smsc.com/media/Downloads_Public/Data_Sheets/9116.pdf >> > > 9116 seems to use memory mapped regs, while 91c96 [1] page 39 shows it > to use banked register access. So unfortunately, SMC911X would not > support this chip as I cannot even see the banked registers in > smc911x.[ch]. so unfortuantely, I cant switch to SMC911X driver and > will have to wait till lan91c96.c becomes NET_MULTI to be able to > remove the warning in sdp3430 build. > > I guess I misunderstood in thinking that you'd switched chips on the board design. > In fact, I think the following boards use the legacy LAN91C96 driver: > include/configs/apollon.h > include/configs/assabet.h > include/configs/B2.h > include/configs/gcplus.h > include/configs/lubbock.h > include/configs/omap1510inn.h > include/configs/omap1610h2.h > include/configs/omap1610inn.h > include/configs/omap2420h4.h > include/configs/omap5912osk.h > include/configs/omap730p2.h > to confirm a non ti board which uses this legacy chip, I tried > building B2, and yep, I see the same warning which was plaguing me > :(.. > > Do let me know if there are alternatives available. > > The alternative that most immediately jumps to mind is for you to convert the LAN91C96 driver to NET_MULTI :) It's pretty easy to do and would help the "community" in a big way. > Regards, > Nishanth Menon > > Ref: > [1] http://www.embeddedsys.com/subpages/resources/images/documents/LAN91C96_datasheet.pdf > regards, Ben