From owner-freebsd-hackers Tue Dec 19 12: 6: 9 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 19 12:06:06 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 8DA5837B400 for ; Tue, 19 Dec 2000 12:06:06 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id NAA00953 for ; Tue, 19 Dec 2000 13:03:42 -0700 (MST) Received: from 206-132-48-12.nas-1.SCF.primenet.com(206.132.48.12), claiming to be "max" via SMTP by smtp03.primenet.com, id smtpdAAAMzaqWb; Tue Dec 19 13:03:32 2000 Reply-To: From: "Steve Shoecraft" To: Subject: RE: FreeBSD vs Linux, Solaris, and NT Date: Tue, 19 Dec 2000 13:08:31 -0700 Message-ID: <000001c069f7$767b3b00$0c3084ce@max.home.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: <200012191838.KAA13083@implode.root.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are a number of reasons why a manufacturer can not/will not release source code for a driver. A few that come to mind are: a) A device driver is a reflection of the hardware. Manufacturers in highly competitive markets could potentially be giving away trade secrets for their new wiz-bang technology by publishing the source code. b) Manufacturers license technology from other manufacturers for inclusion into their product. The license/NDA does not allow them to disseminate the information (either through source or documentation). I can completely understand their position. If *I* were doing business in a highly competitive marketplace, I would be VERY weary of publishing my proprietary information for my competitors to see. EXAMPLE: I have been trying to deal with ATI recently regarding my All-In-Wonder 128 and TV-Out. Although they have been *VERY* helpful in giving me example source and datasheets for the R128 chipset, they cannot give me the information on how to enable TV-Out. This is because the ImpactTV chipset on my AIW contains technology licensed from Macrovision, and for them (ATI) to release the information to me would breach their agreement with Macrovision and open them up to a nice fat lawsuit. I *MAY* have to try and get a license from Macrovision and then present my licensing info to ATI -- and even if I did, I would not be able to distribute the source for that component of the driver... (sigh) IMHO, we should more than happy if a manufacturer supplies us with drivers, even if they are in binary form. If they release the source code/datasheets for a device, fantastic. Personally, I'd rather have the driver for the latest piece of hardware than wait several years until they feel releasing the info wouldn't hurt them in the marketplace. - Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message