From owner-freebsd-questions@FreeBSD.ORG Sat Dec 13 09:44:29 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCC3B1065672 for ; Sat, 13 Dec 2008 09:44:29 +0000 (UTC) (envelope-from perrin@apotheon.com) Received: from outbound-mail-154.bluehost.com (outbound-mail-154.bluehost.com [67.222.39.34]) by mx1.freebsd.org (Postfix) with SMTP id 9BE218FC22 for ; Sat, 13 Dec 2008 09:44:29 +0000 (UTC) (envelope-from perrin@apotheon.com) Received: (qmail 28449 invoked by uid 0); 13 Dec 2008 09:43:56 -0000 Received: from unknown (HELO box183.bluehost.com) (69.89.25.183) by outboundproxy5.bluehost.com with SMTP; 13 Dec 2008 09:43:56 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=apotheon.com; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:Mime-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent:X-Identified-User; b=gDAA3Vyo7xoHBK53+/Xe+RLODMttD0gGOUEk+i0VyxhZAUQmUcdf2wyrxuH/wZ60H3LUXCe2hnsATP8Zev9yymxxtPWebO8rEGR4c3mqJdGSV9Q7k8H8MhcrBMB/mx5Y; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kokopelli.hydra) by box183.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LBR2z-0005HM-7B for freebsd-questions@freebsd.org; Sat, 13 Dec 2008 02:44:29 -0700 Received: by kokopelli.hydra (sSMTP sendmail emulation); Sat, 13 Dec 2008 02:44:03 -0700 Date: Sat, 13 Dec 2008 02:44:03 -0700 From: Chad Perrin To: freebsd-questions@freebsd.org Message-ID: <20081213094403.GH39031@kokopelli.hydra> Mail-Followup-To: freebsd-questions@freebsd.org References: <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> <20081212203202.H4803@wojtek.tensor.gdynia.pl> <20081212150228.520ad7f8@scorpio> <20081212212931.F5072@wojtek.tensor.gdynia.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tcC6YSqBgqqkz7Sb" Content-Disposition: inline In-Reply-To: <20081212212931.F5072@wojtek.tensor.gdynia.pl> User-Agent: Mutt/1.4.2.3i X-Identified-User: {737:box183.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Subject: Re: Why FreeBSD not popular on hardware vendors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 09:44:29 -0000 --tcC6YSqBgqqkz7Sb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 12, 2008 at 09:35:59PM +0100, Wojciech Puchar wrote: > >>NVidia MUST INCLUDE full documentation of their hardware. > >>this is normal - hardware manufacturer produces hardware, programmers > >>do make support for it. > >> > >>what is common today isn't normal. > > > >I honestly have no idea what you are trying to communicate here. >=20 > exactly what i wrote. the problem is that people like You (and millions > others) are willing to buy product without any documentation. You may find this surprising, but sometimes circumstances lead people to make purchases of "total package" products rather than building something piecemeal or being able to specify what goes into a purchase at a very fine-grained level. Laptop purchases in particular suffer the problem of tending to be preconfigured package deals -- and sometimes you have to compromise on getting fully documented hardware with open specs in order to meet other requirements that are more critical to your immediate needs. This may especially be a problem for people who need a known-good physical interface to stave off repetitive stress injury (for example). Then again, judging by some of your statements, you probably feel that laptops should never be used with FreeBSD unless they've been repurposed as file servers. >=20 > if you think they do this to hide their hardware secrets you are wrong. > See x86 instruction set - does it reveal how Intel or Amd made their=20 > processor so fast? no! >=20 > They do this to hide their hardware faults that way - that's the true=20 > reason they do this. >=20 > With new hardware produced every year it MUST be buggy and certainly ther= e=20 > are thousands of hardware bugs. >=20 > with "secret" drivers - they can easily hide them. AFAIK at least half of= =20 > their driver code are to do workaround of their hardware bugs. I rather suspect that a much stronger, and more common, reason for obstinate refusal to open specs is the short-sightedness and general ignorance of daycoders and pointy-haired bosses -- all of whom think Java is the best programming language around because that's what "most" programmers use and have some vague, unsupported (but stubborn) notion that secrets are good for business. At least it *seems* they all think so. --=20 Chad Perrin [ content licensed OWL: http://owl.apotheon.org ] A: It reverses the normal flow of conversation. Q: What's wrong with top-posting? --tcC6YSqBgqqkz7Sb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklDg+MACgkQ9mn/Pj01uKXBUgCggUsbnQLcMW5Ak4YzFpG3XIua OCoAoOhJV2R9OIUHKKM0G1HfPtRKADtm =MQG2 -----END PGP SIGNATURE----- --tcC6YSqBgqqkz7Sb--