From owner-freebsd-hackers Wed Mar 29 8: 9:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id B17AF37B5CD for ; Wed, 29 Mar 2000 08:09:22 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id JAA3004707 for ; Wed, 29 Mar 2000 09:09:21 -0700 (MST) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id JAA02527 for ; Wed, 29 Mar 2000 09:09:20 -0700 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 29 Mar 2000 09:09:20 -0700 (MST) From: "Ronald G. Minnich" X-Sender: rminnich@mini.acl.lanl.gov To: hackers@freebsd.org Subject: How good a job of PCI config will freebsd do? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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? 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. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message