From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Steve.Glendinning@smsc.com
Cc: netdev@vger.kernel.org, Ian.Saturley@smsc.com
Subject: Re: Extend smc911x to support LAN921x chips - differences?
Date: Tue, 9 Sep 2008 18:18:47 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.0809091814460.7385@axis700.grange> (raw)
In-Reply-To: <OFFEAB9876.D4A121DB-ON802574BF.0052D905-802574BF.0054D4AE@smsc.com>
Hi Steve,
On Tue, 9 Sep 2008, Steve.Glendinning@smsc.com wrote:
> Did you have the in-tree driver succesfully working with LAN9115?
I haven't used smc911x for a while, but last time I used it (around
2.6.21, I think), I think, it worked. Was a completely different hardware
though.
> The only hardware difference between the two is that LAN921[5678] has an
> Auto-MDIX PHY. This adds a configuration bit in one of the
> vendor-specific
> PHY registers to force the feature off, but it defaults to Auto-MDIX
> enabled.
> All of the SCR and MAC registers (and the remaining PHY registers) are
> *identical*, so any working driver should just need the ID register
> changing to recognise the newer part.
It works now! Just chose a wrong bus-width.
> Early revisions of LAN911X had a hardware bug which is most commonly
> experienced when joining/leaving multicast groups. The smsc911x driver
> contains a workaround for this, but the in-tree driver does not. LAN921X
> came after this was fixed in hardware, so this workaround is not
> necessary.
>
> The vast majority of users i've worked with have ended up using the
> out-of-tree smsc911x driver, as it "just works" on many platforms.
> I'll be re-submitting another candidate when I've finished working on the
> LAN9500 USB ethernet driver, but for now the latest submission:
>
> http://marc.info/?l=linux-netdev&m=121240395122475&w=2
Thanks, I was about to try yours, was the last attempt to use the stock
driver, and, perhaps, unfortunately for you, it worked:-)
Thanks again
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
next prev parent reply other threads:[~2008-09-09 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 15:26 Extend smc911x to support LAN921x chips - differences? Steve.Glendinning
2008-09-09 16:18 ` Guennadi Liakhovetski [this message]
2008-09-09 20:08 ` Peter Korsgaard
2008-10-10 23:33 ` [PATCH, RFC] Extend smc911x to support LAN921x chips Guennadi Liakhovetski
2008-10-11 7:22 ` Peter Korsgaard
2008-10-11 9:00 ` Guennadi Liakhovetski
2008-10-11 16:48 ` Peter Korsgaard
2008-10-11 20:30 ` Guennadi Liakhovetski
2008-10-12 7:38 ` Peter Korsgaard
2008-10-11 21:10 ` [PATCH] smc911x: Fix external PHY detection Guennadi Liakhovetski
2008-10-11 22:07 ` David Miller
2008-10-12 7:43 ` Peter Korsgaard
2008-10-11 21:13 ` [PATCH] smc911x: Add support for LAN921{5,7,8} chips from SMSC Guennadi Liakhovetski
2008-10-11 22:08 ` David Miller
2008-10-11 22:59 ` [PATCH v2] " Guennadi Liakhovetski
2008-10-12 7:54 ` Peter Korsgaard
2008-10-13 4:05 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-09-09 14:00 Extend smc911x to support LAN921x chips - differences? Guennadi Liakhovetski
2008-09-09 14:45 ` Guennadi Liakhovetski
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=alpine.DEB.2.00.0809091814460.7385@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=Ian.Saturley@smsc.com \
--cc=Steve.Glendinning@smsc.com \
--cc=netdev@vger.kernel.org \
/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