From owner-freebsd-hackers Fri Jun 16 0:51:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7D26937B9A9; Fri, 16 Jun 2000 00:51:14 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA26379; Fri, 16 Jun 2000 09:51:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Ronald G Minnich , hackers@FreeBSD.ORG Subject: Re: freebsd bios. In-reply-to: Your message of "Thu, 15 Jun 2000 18:37:51 PDT." <200006160137.SAA01345@mass.osd.bsdi.com> Date: Fri, 16 Jun 2000 09:51:08 +0200 Message-ID: <26377.961141868@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The key is that freebsd may need to change a few things to make it >> bootable from cold hardware. I don't think this is for sure, but it may >> happen. I hope the team is receptive to such changes ... > >ie. "LinuxBIOS won't initialise the system correctly, so you'd better >clean up after it"? How is the microcode loading handled in LinuxBIOS ? As far as I know getting hold of the microcode-supplemental data from Intel is a process which is (impossible - epsilon) and certainly not open source compatible ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message