From owner-freebsd-hackers  Thu Apr  3 09:01:42 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA02545
          for hackers-outgoing; Thu, 3 Apr 1997 09:01:42 -0800 (PST)
Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA02537
          for <hackers@freebsd.org>; Thu, 3 Apr 1997 09:01:32 -0800 (PST)
Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id MAA02283; Thu, 3 Apr 1997 12:04:45 -0500 (EST)
Message-Id: <3.0.32.19970403115910.00b89450@etinc.com>
X-Sender: dennis@etinc.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Thu, 03 Apr 1997 11:59:12 -0500
To: Narvi <narvi@haldjas.folklore.ee>,
        Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
From: dennis <dennis@etinc.com>
Subject: Re: Does de driver do 100MBIT Full Duplex?
Cc: hackers@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 09:10 AM 4/3/97 -0500, dennis wrote:
>At 10:23 AM 4/3/97 +0300, Narvi wrote:
>>
>>
>>On Wed, 2 Apr 1997, J Wunsch wrote:
>>
>>> As dennis wrote:
>>> 
>>> > Is the driver that you send me directly for 2.1.7 (that worked
>>> > beautifully) in 2.2.1R? If not, WHY NOT!
>>> 
>>> No need to shout.  We aren't deaf exactly.
>>> 
>>> Since Matt released it _after_ 2.2 has been cut.  I've got a very
>>> explicit message from Matt when i've been asking him earlier (right in
>>> time to get something into 2.2 still) about a new version, that he
>>> considered the stuff that sneaked into NetBSD by that time too buggy
>>> to see it officially in FreeBSD.  That's why we've been integrating
>>> the little hack still to make at least the DE21140A supported.  We
>>> originally deferred the inclusion of this patch in anticipation of the
>>> new driver version.

It seems to me, that the fact that the most popular driver for FreeBSD
doesn't work is a sufficient condition to hold up the release until it
does.

What you have now is a release that was supposed to be a "great
saviour" feature-wise that is fundamentally unusable in its released
form for a large number of users.....

Dennis