Netdev List
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: netdev@vger.kernel.org
Subject: Extend smc911x to support LAN921x chips - differences?
Date: Tue, 9 Sep 2008 16:00:18 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0809091307160.6470@axis700.grange> (raw)

Hi,

I have to support the LAN9215 chip from SMSC under Linux. Of course, there 
is the manufacturer provided smsc911x driver, that supports both chip 
families, but I would prefer to extend the mainline smc911x driver to also 
support 921x. I have both datasheets, they are freely downloadable from 
SMSC site, and I have both drivers, but they are absolutely different. To 
make my decision and the work easier - maybe someone knows from the top of 
their head, what the relevant differences between the chips are?

The vendor driver does not really differentiate between the chips. It does 
read the chip version, and sets the "generation" variable, but then that 
variable is only used once to rule out the oldest chips, which anyway are 
not supported by smc911x. So I tried the in-kernel driver with only added 
chip IDs added, it can access registers, read and write the MAC-address, 
interrupts are generated too, but so far I see nothing on the wire, and 
the PHY reports "link down".

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer

             reply	other threads:[~2008-09-09 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 14:00 Guennadi Liakhovetski [this message]
2008-09-09 14:45 ` Extend smc911x to support LAN921x chips - differences? Guennadi Liakhovetski
  -- strict thread matches above, loose matches on Subject: below --
2008-09-09 15:26 Steve.Glendinning
2008-09-09 16:18 ` Guennadi Liakhovetski
2008-09-09 20:08 ` Peter Korsgaard

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=Pine.LNX.4.64.0809091307160.6470@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --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