From owner-freebsd-hackers Mon Jun 19 15:55:55 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 4F53337B8C7 for ; Mon, 19 Jun 2000 15:55:51 -0700 (PDT) (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 QAA1002071 for ; Mon, 19 Jun 2000 16:55:50 -0600 (MDT) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id QAA01834 for ; Mon, 19 Jun 2000 16:55:50 -0600 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Mon, 19 Jun 2000 16:55:50 -0600 (MDT) From: Ronald G Minnich X-Sender: rminnich@mini.acl.lanl.gov To: hackers@FreeBSD.ORG Subject: Re: freebsd bios. In-Reply-To: <66205.961453079@pinhead.parag.codegen.com> 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 On Mon, 19 Jun 2000, Parag Patel wrote: > It's fairly simple, other than dealing with the > various motherboard/chipset vagaries. So far those vagaries are not much code, something like 200 lines tops. > It's possible to make a complete BIOS based on Linux that in turn loads > and boots another kernel, but that I don't think that this is what the > LinuxBIOS folks are attempting. Actually, we aren't attempting it, we've got it working. see the LOBOS paper on the www.linuxbios.org web page. One option is that we start linux from NVRAM, talk to a DHCP server, and as a result we suck a kernel down over the network and boot it. Linux (or FreeBSD) make far more capable network boot programs than such things as PXE. And LinuxBIOS is SMALLER than the Intel BIOS it replaces. You can get complicated. LinuxBIOS loads, talks to DHCP, is sent some KLDs, the KLDs drive the boot device, and so on. So the thing in NVRAM can be little more than a netboot. A number: sun's net bootstrap is 200K. > Instead they have (or will have) access to the flash from within Linux > to load a kernel directly into flash (along with its startup code) > rather than placing it into /. (Please correct me if I'm wrong.) You have both options. We're going to use them. > Personally, I'd set it up to hold two kernel images - one for testing > and one for emergency recovery. If a bad kernel gets into the flash, > recovering will be ... painful. But there may not be enough room. There will be enough in future, next generation mainboards have 2 MB or more flash. My cheap DFI mainboard at home has 2 MB flash. For now, there is enough room in current mainboards, and more to come (I am told that the current driver for flash is MP3 players, which only demand more and more and more and ...) ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message