public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Thomas Zehetbauer <thomasz@hostmaster.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tulip driver still broken
Date: Wed, 01 Aug 2001 08:51:47 -0700	[thread overview]
Message-ID: <3B682593.AB3D143C@candelatech.com> (raw)
In-Reply-To: <20010731001907.A21982@hostmaster.org> <3B66B13B.28BD0324@nortelnetworks.com>

Chris Friesen wrote:
> 
> Thomas Zehetbauer wrote:
> >
> > My genuine digital network interface card ceased to work with the tulip
> > driver contained in kernel revisions >= 2.4.4 and the development driver from
> > sourceforge.net.
> 
> How is the sourceforge driver different than the one at www.scyld.com?
> 

Becker (Scyld) has only recently gotten his drivers to even compile
on 2.4 kernel, and they are still beta quality for 2.4, evidently.

There seem to be attempts to keep the drivers in sync, functionally,
but the architectures have diverged quite a lot...

Ben

-- 
Ben Greear <greearb@candelatech.com>          <Ben_Greear@excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

  parent reply	other threads:[~2001-08-01 15:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 22:19 tulip driver still broken Thomas Zehetbauer
2001-07-30 22:57 ` Joshua Schmidlkofer
2001-07-30 23:09   ` Jeff Garzik
2001-07-30 23:30     ` Michal Jaegermann
2001-08-01 14:36     ` Patrick Cole
2001-07-31 13:23 ` Chris Friesen
2001-07-31 18:00   ` Jeff Garzik
2001-08-01 15:51   ` Ben Greear [this message]
2001-08-01 16:45     ` joseph.bueno
2001-08-01 21:14       ` Justin Guyett
2001-08-02  7:35         ` joseph.bueno
2001-08-01 21:52       ` Jeff Garzik

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=3B682593.AB3D143C@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomasz@hostmaster.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