From: Ben Greear <greearb@candelatech.com>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Jason Lunz <lunz@gtf.org>, linux-kernel@vger.kernel.org
Subject: Re: NAPI patch against 2.4.18
Date: Sun, 07 Jul 2002 18:32:22 -0700 [thread overview]
Message-ID: <3D28EBA6.8040400@candelatech.com> (raw)
In-Reply-To: 1026088234.1283.246.camel@tux
Martin Josefsson wrote:
> On Sun, 2002-07-07 at 21:15, Jason Lunz wrote:
>
>>greearb@candelatech.com said:
>>
>>>Does anyone have a working NAPI kernel and tulip driver patch against
>>>2.4.18 or so? I will be happy to test this if so.
>>
>>Yes, I backported the core last week to 2.4.19-rc1 from 2.5.24, but the
>>patch ought to apply to 2.4.18 with only offset mismatches. I kept a lot
>>of style cleanups in the patch, but they should be easy to remove if
>>they cause problems. I'll be backporting the various napified drivers to
>>2.4 this week.
>>
>>http://orr.falooley.org/pub/linux/net/
>
>
> Why not use the original patch?
>
> ftp://robur.slu.se/pub/Linux/net-development/NAPI/
The only patches I found there were about 6 months old, and the tulip
patch seems to be based on the tulip driver in 2.4.2. The tulip driver
did not reach stability in the 2.4 series untill about 2.4.9, when it
finally started auto-negotiating correctly.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
prev parent reply other threads:[~2002-07-08 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 17:43 NAPI patch against 2.4.18 Ben Greear
2002-07-07 19:15 ` Jason Lunz
2002-07-08 0:30 ` Martin Josefsson
2002-07-08 1:32 ` Ben Greear [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=3D28EBA6.8040400@candelatech.com \
--to=greearb@candelatech.com \
--cc=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=lunz@gtf.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