public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Johan Kullstam" <kullstam@ne.mediaone.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.1-pre11 de2104X tulip driver problem
Date: 13 Dec 2001 19:23:31 -0500	[thread overview]
Message-ID: <m2bsh2ps3g.fsf@euler.axel.nom> (raw)
In-Reply-To: <20011213150346.A31843@Sophia.soo.com> <m2hequpw3a.fsf@euler.axel.nom> <3C193AD3.55AFF698@mandrakesoft.com>
In-Reply-To: <3C193AD3.55AFF698@mandrakesoft.com>

Jeff Garzik <jgarzik@mandrakesoft.com> writes:

> Johan Kullstam wrote:
> > i have a DEC DE450 (based on 21041 AA chipset).  i guess, for
> > 2104[01], tulip driver has been broken since 2.4.4 (yes, that's over
> > six months of brokeness).  yes, jeff garzik knows about it.  i've
> > emailed the list and sourceforge &c.
> 
> This is a bug report for de2104x not tulip.  de2104x was created to fix
> the 2104x problems in tulip, which is getting really hairy to
> maintain.

ah ok.  sorry to crap on you.  i guess the proliferation of tulip
clones is getting pretty crazy.

i got a switch over the weekend.  my DE500 (DEC 21140AB w/o MII)
wouldn't negotiate full-duplex.  i finally just broke down and
scrapped my tulips and put in a 3com905b instead.

-- 
J o h a n  K u l l s t a m
[kullstam@mediaone.net]

  reply	other threads:[~2001-12-14  0:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13 20:03 2.5.1-pre11 de2104X tulip driver problem really mason@soo.com
2001-12-13 22:57 ` Johan Kullstam
2001-12-13 23:33   ` Jeff Garzik
2001-12-14  0:23     ` Johan Kullstam [this message]
2001-12-13 23:36 ` 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=m2bsh2ps3g.fsf@euler.axel.nom \
    --to=kullstam@ne.mediaone.net \
    --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