Date: Tue, 18 Mar 2008 13:11:34 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: freebsd-hackers@freebsd.org Subject: Re: Re[2]: vkernel & GSoC, some questions Message-ID: <20080318130927.D17188@fledge.watson.org> In-Reply-To: <20080318074332.GS44676@server.vk2pj.dyndns.org> References: <20080316122108.S44049@fledge.watson.org> <E1JatyK-000FfY-00.shmukler-mail-ru@f8.mail.ru> <200803162313.m2GNDbvl009550@apollo.backplane.com> <3c0b01820803171243k5eb6abd3y1e1c44694c6be0f6@mail.gmail.com> <200803172016.m2HKGfjA020263@apollo.backplane.com> <20080318074332.GS44676@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 18 Mar 2008, Peter Jeremy wrote: >> with the BIOS, and see BIOSes then respec to a new far cleaner API. >> The >> BIOS is the stinking pile of horseshit that has held back OS development >> for the last 15 years. > > I'd go further and say that BIOSes are getting worse: Back in the AT-clone > days, you could just totally ignore the BIOS once you'd gotten the kernel > loaded. Now you _have_ to keep talking to the BIOS for things like ACPI - > but the BIOSes are still just as broken as they used to be. On Sun's Niagara (sun4v) platform, it is expected that all OS's will sit on top of the hypervisor that ships in the firmware, abstracting away countless basic hardware services behind hypercalls. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080318130927.D17188>