linux-kernel - Re: driver support for Chelsio T210 10Gb ethernet in 2.6.x

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

Date:	Wed, 15 Nov 2006 17:03:20 -0800
From:	Stephen Hemminger <shemminger@...l.org>
To:	Chris Stromsoe <cbs@....ucla.edu>
Cc:	Jeff Garzik <jeff@...zik.org>, "Felix Marti" <felix@...lsio.com>,
	linux-kernel@...r.kernel.org
Subject: Re: driver support for Chelsio T210 10Gb ethernet in 2.6.x

I took the latest Chelsio driver and gave it a TOE lobotomy so here
is a version to test, it is large so see git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/chelsio-2.6.git

This is a clone of jeff's netdev-2.6 tree, and the chelsio stuff is on
the chelsio branch.

This took me an afternoon, so I don't see why Chelsio didn't do it.

    Port of Chelsio's 2.2.0 version driver from:
        http://service.chelsio.com/drivers/linux/t210/cxgb2toe-2.2.0.tar.gz
    
    De-vendorized:
        - removed all TCP Offload Engine support because those changes
          will not be accepted in mainline kernel.
        - new files run through Lindent
        - removed code that was '#ifdef' for older kernel versions
        - fix for 2.6.19 irq
        - replace usage of TSC with ktime
        - remove /proc trace debug stuff
        - remove dead code
        - incorporate GSO, etc.
        - get rid of FILE_IDENT() macro
        - fix sparse warnings by adding __iomem and __user
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/