From owner-freebsd-hackers Tue Mar 28 7:32:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 0D8A037B55D for ; Tue, 28 Mar 2000 07:32:42 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id KAA21626; Tue, 28 Mar 2000 10:33:24 -0500 (EST) Message-Id: <200003281533.KAA21626@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 28 Mar 2000 10:28:53 -0500 To: Blaz Zupan From: Dennis Subject: Re: Onboard Intel NIC Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: References: <200003271926.OAA18569@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Its an important driver. People get upset when they can't run full-duplex >> mode. It makes linux MUCH more attractive when you can run your $39. card >> at twice the speed. > >I run the Intel Etherexpress in full duplex without any problems. obviously not the one that has the error. Are you paying attention? > >> Whether you are angry at me or not is no reason to punish the communiity. >> If you think that you are just doing this for me because I'm the only one >> with the nerve to complain then you dont understand your obligation to the >> user base. > >OBLIGATION? Excuse me? > >> Plus I've already fixed it myself. So if you fix it its not for me at all. > >Have you contributed the fix to FreeBSD? I think I know the answer. I passed on the info to DG on how to fix it. Work I do belongs to my company because they pay me to do it. I know few of you understand that, So unless you want to attach the "copyright Emerging Technologies" to the driver you cant use it. db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message