netdev - Re: [PATCH] tc35815 driver update (take 2)

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

Date:	Tue, 06 Mar 2007 06:20:04 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Atsushi Nemoto <anemo@....ocn.ne.jp>
CC:	linux-mips@...ux-mips.org, ralf@...ux-mips.org,
	netdev@...r.kernel.org, sshtylyov@...mvista.com
Subject: Re: [PATCH] tc35815 driver update (take 2)

Atsushi Nemoto wrote:
> Current tc35815 driver is very obsolete and less maintained for a long
> time.  Replace it with a new driver based on one from CELF patch
> archive.
> 
> Major advantages of CELF version (version 1.23, for kernel 2.6.10) are:
> 
> * Independent of JMR3927.
>   (Actually independent of MIPS, but AFAIK the chip is used only on
>    MIPS platforms)
> * TX4938 support.
> * 64-bit proof.
> * Asynchronous and on-demand auto negotiation.
> * High performance on non-coherent architecture.
> * ethtool support.
> * Many bugfixes and cleanups.
> 
> And improvoments since version 1.23 are:
> 
> * TX4939 support.
> * NETPOLL support.
> * NAPI support. (disabled by default)
> * Reduce memcpy on receiving.
> * PM support.
> * Many cleanups and bugfixes.
> 
> Signed-off-by: Atsushi Nemoto <anemo@....ocn.ne.jp>
> 
>  drivers/net/Kconfig     |    3 
>  drivers/net/tc35815.c   | 2587 ++++++++++++++++++++++++++++++++++------------
>  include/linux/pci_ids.h |    2 
>  3 files changed, 1917 insertions(+), 675 deletions(-)

applied to #upstream, let's give it a good review while it hangs out in 
libata-dev.git#ALL and -mm


-
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