Date: Tue, 17 Dec 2002 23:03:19 -0500 From: David Cuthbert <dacut@kanga.org> To: current@freebsd.org Subject: Re: 80386 out of GENERIC Message-ID: <3DFFF387.9050304@kanga.org> In-Reply-To: <20021217194724.A36521@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DFFF387.9050304>