From: Jeff Garzik <jeff@garzik.org>
To: Hayim Shaul <hayim@iportent.com>
Cc: Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org, edward_peng@dlink.com.tw,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18-rc6 1/2] dllink driver: porting v1.19 to linux 2.6.18-rc6
Date: Thu, 13 Sep 2007 00:00:07 -0400 [thread overview]
Message-ID: <46E8B5C7.8060804@garzik.org> (raw)
In-Reply-To: <1157620189.2904.16.camel@localhost.localdomain>
Hayim Shaul wrote:
> Description:
> For DLink Fiber NIC, Linux 2.4.22 ships with driver version 1.19,
> whereas, Linux 2.6.x ship with driver version 1.17.
>
> The following patch upgrades the 2.6.x driver to include changes (and
> bug fixes done until 1.19b).
>
> These fixes are (copied from the driver):
> 1.18 2002/11/07 New tx scheme, adaptive tx_coalesce.
> Remove tx_coalesce option.
> 1.19 2003/12/16 Fix problem parsing the eeprom on big endian
> systems. (philt@4bridgeworks.com)
>
> Disclaimer:
> Since I returned my DLink NIC to the store I couldn't test it
> thoroughly. It seemed to work just as well as v1.17. However, both
> version made the NIC hang after a few minutes.
Please update to the latest upstream kernel (2.6.22 or 2.6.23-rc).
Also, please make sure you do not back out changes included in the
upstream kernel since 2.6.17.
prev parent reply other threads:[~2007-09-13 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 9:09 [PATCH 2.6.18-rc6 1/2] dllink driver: porting v1.19 to linux 2.6.18-rc6 Hayim Shaul
2006-09-07 9:19 ` Arjan van de Ven
2006-09-07 10:52 ` Francois Romieu
2006-09-10 11:10 ` Hayim Shaul
2006-09-21 13:29 ` Florian Weimer
2007-09-13 4:00 ` Jeff Garzik [this message]
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=46E8B5C7.8060804@garzik.org \
--to=jeff@garzik.org \
--cc=edward_peng@dlink.com.tw \
--cc=hayim@iportent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).