From: Jeff Garzik <jgarzik@pobox.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Ondrej Zary <linux@rainbow-software.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: Compex FreedomLine 32 PnP-PCI2 broken with de2104x
Date: Mon, 25 Feb 2008 02:28:14 -0500 [thread overview]
Message-ID: <47C26E0E.2070109@pobox.com> (raw)
In-Reply-To: <20080218032111.GA7970@colo.lackof.org>
Grant Grundler wrote:
> ISTR there was a time when tulip would compete with de4x5 for devices.
> tulip is the preferred driver. That's clearly no longer the case
> and perhaps both distro's need to revisit this.
The only reason why de4x5 still exists is that the /tulip/ driver fails
to work on a few chips like the 21142 (43?) shipped in various alpha boxen.
de4x5 needs to go away, it's been unmaintained for ages, doesn't support
any of the new hotplug APIs.
> de2104x is a "work in progress".
> That's why it's marked "EXPERIMENTAL" in the Kconfig file.
It's not a work in progress, it works just fine for most people (the few
that are left).
Last I heard, there was a problem with non-twisted-pair stuff, but
that's about it.
'experimental' is generally a poorly maintained marker.
Jeff
next prev parent reply other threads:[~2008-02-25 7:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 20:58 Compex FreedomLine 32 PnP-PCI2 broken with de2104x Ondrej Zary
2008-01-30 20:23 ` Ondrej Zary
2008-02-18 3:21 ` Grant Grundler
2008-02-18 16:40 ` Ondrej Zary
2008-02-25 7:15 ` Grant Grundler
2008-02-25 7:30 ` Jeff Garzik
2008-02-26 7:48 ` Grant Grundler
2008-02-25 17:45 ` [PATCH] de2104x: remove BUG_ON() when changing media type Ondrej Zary
2008-02-25 17:52 ` Jeff Garzik
2008-03-24 2:45 ` Grant Grundler
2008-03-24 23:02 ` Ondrej Zary
2008-03-26 15:59 ` Grant Grundler
2008-03-26 18:29 ` Ondrej Zary
2008-03-05 11:27 ` Jeff Garzik
2008-02-25 7:28 ` Jeff Garzik [this message]
2008-02-25 21:31 ` Compex FreedomLine 32 PnP-PCI2 broken with de2104x Ondrej Zary
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=47C26E0E.2070109@pobox.com \
--to=jgarzik@pobox.com \
--cc=grundler@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).