From: Peter Korsgaard <jacmet@sunsite.dk>
To: Steve.Glendinning@smsc.com
Cc: Bahadir Balban <Bahadir.Balban@arm.com>,
Bill Gatliff <bgat@billgatliff.com>,
Dustin Mcintire <dustin@sensoria.com>,
ian.saturley@smsc.com, netdev@vger.kernel.org
Subject: Re: [PATCH] SMSC LAN911x and LAN921x vendor driver
Date: Thu, 02 Aug 2007 00:27:40 +0200 [thread overview]
Message-ID: <87hcnioppf.fsf@p4.be.48ers.dk> (raw)
In-Reply-To: <OF5F9C7C7D.04B8DBCD-ON80257328.0063528D-80257328.0065CB53@smsc.com> (Steve Glendinning's message of "Mon, 30 Jul 2007 19:31:51 +0100")
>>>>> "Steve" == Steve Glendinning <Steve.Glendinning@smsc.com> writes:
Hi,
>> What's the problem with Dustin's driver? It seems to work fine here
>> with a lan9117. Why not just add lan921x support to the existing
>> driver?
Steve> I have heard Dustin's driver works very well on PXA, but on
Steve> others it doesn't even compile (hence why it depends on
Steve> ARCH_PXA).
I'm using it on PPC.
Steve> Dustin's driver was based on the smc91x code, but these two
Steve> ethernet devices share nothing other than a similar name.
Steve> smsc911x is a new, completely platform-independent driver with
Steve> workarounds for several hardware issues, and it doesn't suffer
Steve> from quite as much macro abuse :-)
The macros are not that bad as the hw people sligtly misconnected the
chip, so I need special access routines (enable the big endian mode,
not byteswap on normal registar access and byteswap on fifo access).
I'll give your driver a try and report back.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2007-08-01 22:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 18:54 [PATCH] SMSC LAN911x and LAN921x vendor driver Steve Glendinning
2007-07-18 22:38 ` Jeff Garzik
2007-07-20 16:22 ` Steve.Glendinning
2007-07-29 20:53 ` Peter Korsgaard
2007-07-30 18:31 ` Steve.Glendinning
2007-08-01 22:27 ` Peter Korsgaard [this message]
2007-08-07 23:09 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2008-10-21 13:00 Steve Glendinning
[not found] <20080515170728.GA3176@PTXN0038.genpitfi01.og.ge.com>
2008-05-19 12:34 ` Steve Glendinning
2008-05-19 16:24 ` Catalin Marinas
2008-05-19 19:06 ` Steve.Glendinning
2008-06-02 10:45 ` Steve Glendinning
2008-06-02 15:54 ` Ben Hutchings
2008-06-02 16:09 ` Bill Gatliff
2008-06-02 18:32 ` Peter Korsgaard
2008-06-02 18:30 ` Steve.Glendinning
2008-06-02 19:03 ` Ben Hutchings
2008-06-04 16:34 ` Steve.Glendinning
2008-06-02 18:47 ` Peter Korsgaard
2006-12-30 16:34 Steve Glendinning
2007-01-04 14:42 ` Pierre TARDY
2006-12-04 22:31 Steve Glendinning
2006-07-28 21:38 Francois Romieu
2006-08-01 15:12 ` [PATCH] " Steve Glendinning
2006-08-01 15:33 ` John W. Linville
2006-08-02 19:23 ` Steve.Glendinning
2006-08-02 19:51 ` John W. Linville
2006-08-01 18:28 ` Scott Murray
2006-08-01 19:27 ` Steve.Glendinning
2006-08-01 23:51 ` Scott Murray
2006-08-03 15:26 ` Steve.Glendinning
2006-08-03 21:07 ` Scott Murray
2006-08-01 21:40 ` Francois Romieu
2006-08-02 19:39 ` Steve.Glendinning
2006-08-02 21:07 ` Francois Romieu
2006-08-04 11:29 ` Steve Glendinning
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=87hcnioppf.fsf@p4.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=Bahadir.Balban@arm.com \
--cc=Steve.Glendinning@smsc.com \
--cc=bgat@billgatliff.com \
--cc=dustin@sensoria.com \
--cc=ian.saturley@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.