netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre TARDY <pierre.tardy@freescale.com>
To: Steve Glendinning <steve.glendinning@smsc.com>
Cc: netdev@vger.kernel.org, Ian Saturley <ian.saturley@smsc.com>,
	Bahadir Balban <bahadir.balban@arm.com>
Subject: Re: [PATCH] SMSC LAN911x and LAN921x vendor driver
Date: Thu, 04 Jan 2007 15:42:55 +0100	[thread overview]
Message-ID: <459D126F.5080300@freescale.com> (raw)
In-Reply-To: <11674964822991-git-send-email-steve.glendinning@smsc.com>

Steve Glendinning wrote:
> Attached is a driver for SMSC's LAN911x and LAN921x families of embedded
> ethernet controllers.  There is an existing smc911x driver in the tree;
> this is intended to replace it.
>
> This driver contains workarounds for all known hardware issues, and has
> been tested on all flavours of the chip on multiple architectures.
>
> Dustin McIntire (the author of the smc911x driver) has expressed his
> support for switching to this driver.
>
> Signed-off-by: Steve Glendinning <steve.glendinning@smsc.com>
>   
This patch has just been tested on my Freescale mx31 board, with a 
smsc9117, and Linux version 2.6.16.19.
I agree to include it in mainstream.
old smc911x is restricted to one architecture (PXA) and one chip (9118).

Acked-by: Pierre Tardy <tardyp@gmail.com>




-- 
Pierre Tardy


  reply	other threads:[~2007-01-04 14:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30 16:34 [PATCH] SMSC LAN911x and LAN921x vendor driver Steve Glendinning
2007-01-04 14:42 ` Pierre TARDY [this message]
  -- 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
2007-07-16 18:54 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
2007-08-07 23:09       ` Peter Korsgaard
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=459D126F.5080300@freescale.com \
    --to=pierre.tardy@freescale.com \
    --cc=bahadir.balban@arm.com \
    --cc=ian.saturley@smsc.com \
    --cc=netdev@vger.kernel.org \
    --cc=steve.glendinning@smsc.com \
    /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;
as well as URLs for NNTP newsgroup(s).