From owner-freebsd-current Tue Dec 17 20: 3: 6 2002 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 E233237B401 for ; Tue, 17 Dec 2002 20:03:04 -0800 (PST) Received: from pop016.verizon.net (pop016pub.verizon.net [206.46.170.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24ED343EA9 for ; Tue, 17 Dec 2002 20:02:59 -0800 (PST) (envelope-from dacut@kanga.org) Received: from kanga.org ([151.201.19.185]) by pop016.verizon.net (InterMail vM.5.01.05.20 201-253-122-126-120-20021101) with ESMTP id <20021218040258.DYFN4233.pop016.verizon.net@kanga.org> for ; Tue, 17 Dec 2002 22:02:58 -0600 Message-ID: <3DFFF387.9050304@kanga.org> Date: Tue, 17 Dec 2002 23:03:19 -0500 From: David Cuthbert Organization: Kanga International User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-gb, en-au, en-nz, en-us, en- MIME-Version: 1.0 To: current@freebsd.org Subject: Re: 80386 out of GENERIC References: <24244.1039900460@critter.freebsd.dk> <9710634521.20021214232526@dds.nl> <3DFC0AB1.D60AAF66@mindspring.com> <200212160955.14531.DavidJohnson@Siemens.com> <20021216180948.GD27912@zot.electricrain.com> <3DFFEA03.A27668A8@mindspring.com> <20021217194724.A36521@FreeBSD.org> In-Reply-To: <20021217194724.A36521@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH PLAIN at pop016.verizon.net from [151.201.19.185] at Tue, 17 Dec 2002 22:02:56 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Juli Mallett wrote: > Are you implying that these people, who are undoubtedly adding and > removing lots of things in the kernel, to make things fit, and to > make things do their jobs, can't be bothered to use the appropriate > CPU settings? Not sure where you got that from Terry's post, but... As a sometimes embedded developer (who also runs FreeBSD on his comparatively screaming Athlon desktop box), being able to run FreeBSD, fresh off a CD, on a quirky 386 embedded toaster and have it run perfectly would be a dream. Of course, that's never been the case. As others have mentioned, you're lucky if you have a working BIOS. There's usually no room for "luxuries" like a robust device probing system, a nice, standard PCI bus, queriable hardware, etc. Most of your devices are sitting right on the processor bus (and hopefully you've thrown in enough wait states, but if the thing doesn't respond, spin a bit and hammer it with the request again). As long as it's feasible to compile a kernel for a 386, that's all I could ever home for. Just don't go rewriting the scheduler in assembly and use MMX/SIMD instructions... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message