From: "David S. Miller" <davem@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: jgarzik@mandrakesoft.com, linux-net@vger.kernel.org
Subject: [BETA-0.91] New test release of Tigon3 driver
Date: Wed, 27 Feb 2002 00:03:18 -0800 (PST) [thread overview]
Message-ID: <20020227.000318.02301574.davem@redhat.com> (raw)
Thanks to everyone who has tested and gotten back to us so
far. A new release is up at:
ftp://ftp.kernel.org/pub/linux/kernel/people/davem/TIGON3/tg3-0.91.patch.gz
Older releases will be stored in the "old/" subdirectory.
As before, this is against 2.4.18 but it should be easy to add
this to any other tree.
Brief changelog against 0.91:
[BUG FIX} 5701 and later chips not configured properly for
interrupt handling (me)
[BUG FIX] Try to rectify vital product data read failures
on Dell Vipor boards (me)
[FEATURE] Finish initial implementation of the rest of the ethtool
support. Largely untested. (me+jeff)
[FIX] Add missing PCI/subsystem IDs (jeff)
[FIX] Add missing defines for registers we do not make use
of yet on the card. (me)
[FIX] Add missing IDs and recognition of 5703 boards and PHYs.
[FIX] PCI-X bus speeds not reported properly.
Success/failure reports are appreciated. I would like to note
that the most important thing to tell us is the one line ident
the kernel log gets for each board it probes. Like so:
eth1: Tigon3 [partno(BCM95700A6) rev 7102 PHY(5401)] (PCI:33MHz:64-bit) 10/100/1000BaseT Ethernet 00:04:76:2f:e2:d0
That has all the details we need to see in order to know exactly
what kind of card you have. The lspci dumps are nice, but basically
superfluous :-) Telling us what platform (x86, ppc, alpha, ia64,
etc.) you are on would be appreciated as well.
Thanks again.
next reply other threads:[~2002-02-27 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 8:03 David S. Miller [this message]
2002-02-27 8:15 ` Simon Kirby
2002-02-27 8:22 ` nick
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=20020227.000318.02301574.davem@redhat.com \
--to=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®