From: Jeff Garzik <jgarzik@pobox.com>
To: Timothy I Mattox <tmattox@engr.uky.edu>
Cc: tulip-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [PATCH] tulip, kernel 2.4.26-rc2, 2nd try
Date: Fri, 09 Apr 2004 15:33:19 -0400 [thread overview]
Message-ID: <4076FA7F.7020801@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.43.0404091519200.19041-100000@skyhawk.ecc.engr.uky.edu>
Timothy I Mattox wrote:
> Resubmitting ADMtek Comet MII support patch...
>
> Here is a patch for the tulip driver found in kernel 2.4.26-rc2
> This adds MII functionality to the ADMtek Comet flavor of the tulip,
> specifically, the ability to detect and report the link status with MII.
> This is critical for use with newer channel bonding drivers.
>
> I've tested on several Linksys LNE100TX v4.1 PCI cards, as well as on
> an HP Pavilion N5475 laptop with a built-in NIC that is detected as
> this same model of chip. I have over 750 of this model tulip card in
> use in various beowulf clusters.
>
> This patch was modeled after Donald Becker's tulip.c:v0.98 1/8/2004, but
> the specific bits from his driver have been there for about two years.
> (See: http://sourceforge.net/mailarchive/message.php?msg_id=1841280)
Looks OK, but can you test without netif_carrier_xxx commented out?
I would prefer to leave those active.
Jeff
next prev parent reply other threads:[~2004-04-09 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 20:22 [PATCH] tulip, kernel 2.4.26-rc1 Timothy I Mattox
2004-04-09 19:30 ` [PATCH] tulip, kernel 2.4.26-rc2, 2nd try Timothy I Mattox
2004-04-09 19:33 ` Jeff Garzik [this message]
2004-04-09 19:43 ` Timothy I Mattox
2004-04-09 20:39 ` [PATCH] tulip, kernel 2.4.26-rc2, 3rd try Timothy I Mattox
2004-04-09 20:59 ` Jeff Garzik
2004-04-11 19:37 ` jamal
2004-04-09 19:58 ` [PATCH] tulip, kernel 2.4.26-rc2, 2nd try Francois Romieu
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=4076FA7F.7020801@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=tmattox@engr.uky.edu \
--cc=tulip-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.