Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Dec 2008 14:16:51 -0500
From:      Jerry <gesbbb@yahoo.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: Why FreeBSD not popular on hardware vendors
Message-ID:  <20081212141651.598b287b@scorpio>
In-Reply-To: <ghuau9$juk$1@ger.gmane.org>
References:  <1228733482.4495.14.camel@laptop1.herveybayaustralia.com.au> <20081211103742.21621a6d@gom.home> <20081211190951.GB845@comcast.net> <20081211113257.405a082c@gom.home> <20081211202023.GC845@comcast.net> <20081211134622.15c81ecd@gom.home> <20081212002813.GD32300@kokopelli.hydra> <20081211170011.777236f8@gom.home> <20081212015814.GB32982@kokopelli.hydra> <20081212120437.B3687@wojtek.tensor.gdynia.pl> <20081212181258.GE36348@kokopelli.hydra> <ghuau9$juk$1@ger.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/UGE3XNHAjApxu2lZknrXau=
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, 12 Dec 2008 13:35:46 -0500
Michael Powell <nightrecon@verizon.net> wrote:

>My reservation to the 3D driver thing is it is setting a very dangerous
>precedent if the solution involves allowing a third party commercial
>enterprise to dictate features FreeBSD "must include" before they will
>support it.
>
>In this case with NVidia and the amd64 3D driver let's say for sake of
>argument the developers decide "we want the amd64 3D driver so let's
>go ahead and add in abc_function() and xyz_function(). Later the
>situation is repeated with ATI mandating that abc_function() or
>xyz_function() must be altered to ATI's specs to get ATI 3D
>acceleration. Now you have two commercial companies using FreeBSD as
>the mud puddle in a tug of war game.
>
>Do we really want third parties to have the ability to dictate to the
>devs what code goes into FreeBSD? I have doubts that this is a good
>path.

=46rom my understanding of the requests by NVidia; the changes they asked
for were required to make a fully functional driver. They also stated
that other manufacturers would need/require such code changes also. In
any case, I fail to see what the problem is. Microsoft has make
numerous modifications to its code to enable third party products to
work correctly. With the advent of 'touch screens' now becoming a
reality, along with voice recognition, etc., it seems that FreeBSD
would want to stay ahead of the curve rather than playing catchup.
Heck, unless I am mistaken, the ability to 'hot plug' a USB device does
not even exist in FBSD, although I have heard that work is being done
on it. Unfortunately, the technology has existed for over ten years.

Trying to get hardware vendors interested in your product while
simultaneously telling them to go screw themselves because you have no
intention of working with them does not seem like a workable business
model to me.

--=20
Jerry
gesbbb@yahoo.com

Therefore it is necessary to learn how not to be good, and to use
this knowledge and not use it, according to the necessity of the cause.

	Machiavelli

--Sig_/UGE3XNHAjApxu2lZknrXau=
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAklCuKMACgkQBvaKIJWWCO31pACeL4A6gEzK8bVfp2/mAEn3bvYO
MVoAn3dfaFrCC+gPNOnnN+hXTPdUIJLD
=Ygou
-----END PGP SIGNATURE-----

--Sig_/UGE3XNHAjApxu2lZknrXau=--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081212141651.598b287b>