From: Lech Szychowski <lech.szychowski@pse.pl>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tulip question: tulip.o vs de4x5.o
Date: Tue, 14 Dec 2004 11:10:44 +0100 [thread overview]
Message-ID: <20041214101044.GA8210@lech.pse.pl> (raw)
In-Reply-To: <41A4DF61.8050008@pobox.com>
> >You can actually see the difference on older Alphas: de4x5 works while
> >tulip doesn't transmit or receive a single packet (getting netdev
> >watchdogs later on...).
>
> That's a bug in tulip.
Speaking of bugs in tulip: I am still unable to use tulip driver
from 2.4.28 on my x86 SMP box (Asus P2B-DS) with Adaptec AN-6944A/TX
network card. While de4x5 works fine, with tulip at least one of the
Ethernet interfaces is unable to send/receive packets. More details
available on request.
--
Leszek.
-- lech7@pse.pl 2:480/33.7 -- REAL programmers use INTEGERS --
-- speaking just for myself...
prev parent reply other threads:[~2004-12-14 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 17:28 tulip question: tulip.o vs de4x5.o Justin Piszcz
2004-11-24 7:36 ` Jan-Benedict Glaw
2004-11-24 19:22 ` Jeff Garzik
2004-11-24 19:51 ` Justin Piszcz
2004-12-14 10:10 ` Lech Szychowski [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=20041214101044.GA8210@lech.pse.pl \
--to=lech.szychowski@pse.pl \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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