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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 24 Jun 2009 22:21:58 +0200
From:	Daniel Mack <daniel@...aq.de>
To:	Mike Rapoport <mike@...pulab.co.il>
Cc:	steve.glendinning@...c.com, netdev@...r.kernel.org,
	ARM Linux <linux-arm-kernel@...ts.arm.linux.org.uk>
Subject: Re: smsc9220 with omap3

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. 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.

Daniel

--
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