From owner-freebsd-hackers Wed Mar 29 11: 2:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mg134-053.ricochet.net [204.179.134.53]) by hub.freebsd.org (Postfix) with ESMTP id 0E79837BA71 for ; Wed, 29 Mar 2000 11:02:07 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA01047; Wed, 29 Mar 2000 11:05:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003291905.LAA01047@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ronald G. Minnich" Cc: hackers@freebsd.org Subject: Re: How good a job of PCI config will freebsd do? In-reply-to: Your message of "Wed, 29 Mar 2000 09:09:20 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Mar 2000 11:05:37 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Question, has anyone tried booting freebsd on raw hardware, i.e. absent a > bios? I am curious as to how good a job it can do if, e.g., no enable bits > are set in PIIX4, BARs are not set on PCI devices, no IRQs are assigned, > and so on. Anyone feel they are close enough to this to say? Not good. You'd also have to take care of PCI setup, interrupt routing, any board-specific hacks using the GPIO bits, etc. (eg. on most systems you'll need to turn the CPU fan, power LEDs, etc. on) Doing this without the BIOS is likely to be a major PITA, and different for every single board. Outside of some expensive and boring embedded vendors' products, you're unlikely to get the sort of information you need without reverse-engineering the BIOS that's already there. > See www.acl.lanl.gov/linuxbios to see why I am asking. I see no reason I > could not also put FreeBSD as the BIOS in nvram as well. If you're trying > to build a cluster, you have to kill the BIOS. Well, they're going to have the same basic stuff, and I can see that they're not having much fun trying to get there. I'm curious as to what you mean by "have to kill the BIOS" though; I'm not seeing why it's an issue. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message