netdev - Re: smsc9220 with omap3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 26 Jun 2009 08:53:24 +0300
From:	Tony Lindgren <tony@...mide.com>
To:	Mike Rapoport <mike@...pulab.co.il>
Cc:	Daniel Mack <daniel@...aq.de>, steve.glendinning@...c.com,
	netdev@...r.kernel.org,
	ARM Linux <linux-arm-kernel@...ts.arm.linux.org.uk>
Subject: Re: smsc9220 with omap3

* Mike Rapoport <mike@...pulab.co.il> [090625 08:58]:
> Daniel Mack wrote:
> > On Wed, Jun 24, 2009 at 05:52:16PM +0300, Mike Rapoport wrote:
> >>> We're using that chip connected to a PXA300 and it works well, so I
> >>> wouldn't suspect the driver. Does it work from any other scenario like
> >>> the bootloader? And I don't know OMAP, but it might be helpful to others
> >>> if you posted your platform_data config.
> >> The platform_data I use is:
> >> static struct smsc911x_platform_config smsc911x_config = {
> >> 	.irq_polarity = SMSC911X_IRQ_POLARITY_ACTIVE_LOW,
> >> 	.irq_type = SMSC911X_IRQ_TYPE_PUSH_PULL,
> >> 	.flags = SMSC911X_USE_32BIT | SMSC911X_FORCE_INTERNAL_PHY,
> >> };
> >>
> >> The chip is properly detected, and if I tweak the loopback test to return 0, the
> >>  driver does not complain any more. Moreover, it seems that RX work, at least
> >> ifconfig reports non-zero values for RX packets. Still, there is no even single
> >> packet transmitted from the smsc9220 :(
> >> I suspect that there's some problem with the hardware, and probably someone
> >> encountered similar problems and may have found a solution.
> > 
> > For the electrical part, there is a reference schematic from SMSC.
> 
> Yeah, I know. We actually copied the design from the reference.
> 
> > And on PXA, you need some dumb CMOS logic or a CPLD for proper interfacing
> > of the digital bus. Don't know if the latter is also necessary for OMAP.
> 
> Do you mean that the logic is necessary to demux address and data? If yes, OMAP
> does not need it.
> Besides, we have no problem in CPU <-> lan9220 communications, there's no
> network traffic from the chip. :(

In addition to checking the pin muxing.. Do you have the GPMC configured for
the timings? See arch/arm/mach-omap2/gpmc.c.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html