Date: Thu, 20 Jul 2006 20:32:28 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: "Charles A. Landemaine" <landemaine@gmail.com> Cc: freebsd-hardware@freebsd.org Subject: Re: Improving FreeBSD's hardware compatibility Message-ID: <20060720103228.GA716@turion.vk2pj.dyndns.org> In-Reply-To: <e6575a30607181811x3bedbeeajcaa5d1c0c6ef7293@mail.gmail.com> References: <e6575a30607181811x3bedbeeajcaa5d1c0c6ef7293@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 2006-Jul-18 22:11:45 -0300, Charles A. Landemaine wrote: >Aside from the fact that some vendors don't cooperate to release >hardware specifications, is there something we could do to revert this >situation? I suspect the major problems are lack of interface documentation for the various chips and non-compliance with standards on things like ACPI. I don't believe there's a general solution to the problem, rather work-arounds need to be developed on a case-by-case basis. > How could the community act to change things? Getting action from vendors has been unsuccessful in the past - the Free OS community (Linux + *BSD) is too small for vendors to be concerned about. I suspect the best solution is to publicise configurations that are known to work and what problems exist with other configurations. --=20 Peter Jeremy --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEv1TD/opHv/APuIcRAoAcAJ0a0yhI3Gr92ZLKplUP3Lf4akciuACdEOVF /5iN4sFDvO65dKSYo0FQKlA= =HGmn -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060720103228.GA716>