public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ion Badulescu <ionut@cs.columbia.edu>
To: arjan@fenrus.demon.nl
Cc: linux-kernel@vger.kernel.org, spotter@cs.columbia.edu (Shaya Potter)
Subject: Re: xircom_cb and promiscious mode
Date: Thu, 18 Oct 2001 18:02:13 -0400	[thread overview]
Message-ID: <200110182202.f9IM2Dw30821@buggy.badula.org> (raw)
In-Reply-To: <E15uKqE-0004VS-00@fenrus.demon.nl>

On Thu, 18 Oct 2001 22:36:38 +0100, arjan@fenrus.demon.nl wrote:

> The xircom_tulip_cb driver is more advanced, and probably works well for
> your system. (It doesn't work for all cards, but I suspect that correlates
> highly with the revision that needs the promisc)

In particular the xircom_tulip_cb driver from 2.4.13-pre4 should work well 
at Columbia (since that's one place where I tested it :-). You can simply 
copy the xircom_tulip_cb.c from 2.4.13-pre4 into pretty much any 2.4 
kernel and recompile, and it should work -- except maybe for the 
MODULE_LICENSE line which can be safely commented out.

Arjan, are there still cards that don't work without promisc mode enabled? 
I got two different versions myself and both work very nicely with the 
latest xircom_tulip_cb.

Thanks,
Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.

  reply	other threads:[~2001-10-18 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 21:26 xircom_cb and promiscious mode Shaya Potter
2001-10-18 21:36 ` arjan
2001-10-18 22:02   ` Ion Badulescu [this message]
2001-10-19  0:01   ` Shaya Potter
2001-10-19  0:09     ` Jeff Garzik
2001-11-01 10:26       ` Marc Haber
2001-11-01 15:47         ` Ion Badulescu
2001-11-01 18:34           ` Marc Haber
2001-11-12 18:44             ` Ion Badulescu
2001-11-22 13:29             ` Marc Haber
2001-10-19  0:12     ` 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=200110182202.f9IM2Dw30821@buggy.badula.org \
    --to=ionut@cs.columbia.edu \
    --cc=arjan@fenrus.demon.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spotter@cs.columbia.edu \
    /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