From owner-freebsd-current@FreeBSD.ORG Thu Nov 10 21:12:45 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFE6816A41F for ; Thu, 10 Nov 2005 21:12:45 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D03643D48 for ; Thu, 10 Nov 2005 21:12:45 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1722122 for multiple; Thu, 10 Nov 2005 16:14:51 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAALCTwA069693; Thu, 10 Nov 2005 16:12:42 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 10 Nov 2005 16:02:12 -0500 User-Agent: KMail/1.8.2 References: <20051108232855.2d1b7df5.lists@yazzy.org> <20051109110903.583bb72d.lists@yazzy.org> <4373A384.2020605@cs.okstate.edu> In-Reply-To: <4373A384.2020605@cs.okstate.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511101602.13740.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Reid Linnemann Subject: Re: Generic Kernel API X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2005 21:12:46 -0000 On Thursday 10 November 2005 02:46 pm, Reid Linnemann wrote: > Marcin Jessa wrote: > > Sure, but the point is to use native FreeBSD drivers, even if they were > > in closed source binary form and not drivers written for an entirely > > different O.S. > > > > Marcin > > I'd like to pose my own semi-educated opinion about this topic: > > If hardware vendors are given the ability to provide closed-source, > unfree-licensed binary drivers for hardware, they will probably gladly > do so. They get the bonus of sales to FreeBSD users without having to > give up control or knowledge of their products. They already have the ability to do that and for the most part they don't. Nvidia and Atheros are two companies that do. I think what you are missing here is that regardless of a stable API, having to pay an engineer to learn about that API and the whole "feel" of a given OS and then write and support a driver is not worth the potential FreeBSD sales to most companies. They are only going to provide a driver if they feel they can turn a worthwhile profit doing it, not out of the goodness of their hearts. Currently they can support a rather large chunk of market share if they provide drivers for Windoze, Linux, and maybe OS X. FreeBSD's market share for most folks is just not comparable to those three, so they do not see it as being worth the investment. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org