From: Jeff Garzik <jeff@garzik•org>
To: NetDev <netdev@vger•kernel.org>
Subject: ethtool 2.6.33 released
Date: Wed, 24 Feb 2010 22:35:38 -0500 [thread overview]
Message-ID: <4B85F00A.2050602@garzik.org> (raw)
ethtool version 2.6.33 has been released.
Home page: https://sourceforge.net/projects/gkernel/
Download link:
https://sourceforge.net/projects/gkernel/files/ethtool/2.6.33/ethtool-2.6.33.tar.gz/download
Release notes:
This version introduces a new release numbering scheme, based
on the latest upstream kernel interface supported.
* Fix: several man page corrections
* Feature: rx flow hash configuration
* Feature: report 10000baseT support, where available
* Feature: report MDI-X status, pause auto-neg, link partner
adverts
* Feature: support additional port types
* Feature: support arbitrary speeds, faster than 65535 Mb
* Feature: large and generic receive offload (LRO, GRO) support
* Feature: option to flash firmware image from specified file
* Feature: support for block writing of EEPROMs
* Feature: marvell register dump update
* Feature: at76c50x-usb, e1000e, igb, ixgbe, r8169 register
dump support
* Cleanup: remove support for RX hasing by port (was removed in
kernel by 59089d8d162ddcb5c434672e915331964d38a754)
* Doc: Explicitly ship GPLv2 license, rather than relying
on autotools to supply it for us (autotools started
auto-installing GPLv3 recently)
reply other threads:[~2010-02-25 3:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B85F00A.2050602@garzik.org \
--to=jeff@garzik$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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