From owner-freebsd-hackers Thu Mar 22 12:40:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C4C2F37B742 for ; Thu, 22 Mar 2001 12:40:08 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2MKbrs01583; Thu, 22 Mar 2001 12:37:54 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103222037.f2MKbrs01583@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: scanner@jurai.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-reply-to: Your message of "Thu, 22 Mar 2001 13:15:24 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Mar 2001 12:37:53 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 23 Mar 2001, Daniel C. Sobral wrote: > > > Let me just pipe in a bit. Compromise seems just like the kind of thing > > marketing or legal would want to do. The problem is that _we_ cannot > > compromise because one cannot write a "half-way there" driver. It's a > > technical impossibility. > > I agree 100%. I don't think this will fly either. I am just making the > effort to work with Intel to get what we need. It's not going to happen > overnight. Period. They are not going to change their NDA policy. In the > future maybe. Actually I will forward the email she sent me this last time > after I got off the phone with her an hour ago. I mentioned the problems > Jonathan had with the GigE card. That's why she refers to him. Anyway I > will forward it in a sec to the list. [Speaking here from some experience with this set of issues.] The compromise that you want to strike, and really the *only* compromise that is going to work, is that the *documents* will remain undisclosed, but information from the documents that is necessary to produce a functional, high-performance driver may be disclosed, but *only* through the source code of the driver. Thus one or a small group of people sign the NDA, and keep the documentation. The driver is then developed and maintained by this team, who also have the opportunity to interact with Intel's engineering people. The source code resulting from this effort is then released publically. Intel should probably retain the right to veto code that you might want to put in the driver if they feel that it risks disclosure they don't want, but you don't have to suggest this to them unless you feel you need it as a bargaining chip. This would put them in the same situation as they are already in with their source-available Linux driver; it should not present any more intellectual property risks than they already face, and as a bonus, it gets us a better-supported driver. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message