From owner-freebsd-hardware Sun Dec 29 09:30:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA05837 for hardware-outgoing; Sun, 29 Dec 1996 09:30:10 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA05830 for ; Sun, 29 Dec 1996 09:30:08 -0800 (PST) From: BRETT_GLASS@infoworld.com Received: from ccgate.infoworld.com (ccgate.infoworld.com [192.216.49.101]) by lserver.infoworld.com (8.8.4/8.8.4/GNAC-GW-2.1) with SMTP id JAA24582; Sun, 29 Dec 1996 09:29:55 -0800 (PST) Received: from ccMail by ccgate.infoworld.com (SMTPLINK V2.11) id AA851880339; Sun, 29 Dec 96 10:20:22 PST Date: Sun, 29 Dec 96 10:20:22 PST Message-Id: <9611298518.AA851880339@ccgate.infoworld.com> To: "Rodney W. Grimes" , brandon@glacier.cold.org Cc: freebsd-hardware@freebsd.org Subject: Re: AHA 2940UW? Linux works.. Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > You didn't saymuch else about the hardware, and ``it'll run Linux'' > doesn't tell me much, as Linux does not do a lot of the performance > enhancements in FreeBSD that requires _CORRECTLY_ designed boards. You're right, of course. However, it would be nice if FreeBSD were able to adapt to some common problems it doesn't handle yet -- such as the bug in some RZ1000 chips. (I've been lucky so far, in that most of the motherboards I've worked with have let me disable the part of the chip that poses the problem. But FreeBSD really should handle this one.) --Brett