From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] pc boot and ether drivers Date: Wed, 17 Nov 2004 23:10:42 -0800 From: geoff@collyer.net In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-tzbuorkmdjmgeldhmugjhgvaln" Topicbox-Message-UUID: 066c0660-eace-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-tzbuorkmdjmgeldhmugjhgvaln Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit That's just plan9.ini with data supplied by a different boot loader, presumably at a different memory address. I'd rather have the kernel pick the first (supported) ethernet interface in the PCI tables and use that to boot load via /cfg/pxe, thus putting the plan9.ini's in one place. --upas-tzbuorkmdjmgeldhmugjhgvaln Content-Type: message/rfc822 Content-Disposition: inline Received: from collyer.net ([216.240.55.183]) by collyer.net; Wed Nov 17 19:55:40 PST 2004 Received: from mail.cse.psu.edu ([130.203.4.6]) by collyer.net; Wed Nov 17 19:55:39 PST 2004 Received: from psuvax1.cse.psu.edu (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 2E7FCC6744 for ; Wed, 17 Nov 2004 22:55:38 -0500 (EST) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: from localhost (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id AA04263EA9 for <9fans@cse.psu.edu>; Wed, 17 Nov 2004 22:54:55 -0500 (EST) Received: from mail.cse.psu.edu ([127.0.0.1]) by localhost (psuvax1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14447-01-4 for <9fans@cse.psu.edu>; Wed, 17 Nov 2004 22:54:53 -0500 (EST) Received: from gau.lava.net (gau.lava.net [64.65.64.28]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id C891963E3A for <9fans@cse.psu.edu>; Wed, 17 Nov 2004 22:54:52 -0500 (EST) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by gau.lava.net (Postfix) with ESMTP id E2B52172A9 for <9fans@cse.psu.edu>; Wed, 17 Nov 2004 17:54:51 -1000 (HST) Date: Wed, 17 Nov 2004 17:54:51 -1000 (HST) From: Tim Newsham To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] pc boot and ether drivers In-Reply-To: <6b8af63a9aff0dbdbf3f1a2166f9943e@collyer.net> Message-ID: References: <6b8af63a9aff0dbdbf3f1a2166f9943e@collyer.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces+geoff.9fans=collyer.net@cse.psu.edu Errors-To: 9fans-bounces+geoff.9fans=collyer.net@cse.psu.edu > Command line to what? The kernels don't have command lines. Many boot loaders provide arguments to the booting kernel. I don't think it should be very difficult to craft a command line such as: 9pcdisk bootdisk=local!#S/sdC0/fs *nomp=1 monitor=multisync75 vgasize=1024x768x8 parsing this out from a single argument buffer should be a trivial addition to the current sources. Looks like getting at this data is pretty simple: http://www.gnu.org/software/grub/manual/multiboot/html_node/Boot-information-format.html#Boot%20information%20format Tim N. --upas-tzbuorkmdjmgeldhmugjhgvaln--