From owner-freebsd-hackers Wed Apr 26 10: 0:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-132.dsl.snfc21.pacbell.net [63.202.176.132]) by hub.freebsd.org (Postfix) with ESMTP id A74E537BEA3 for ; Wed, 26 Apr 2000 10:00:24 -0700 (PDT) (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 KAA03066; Wed, 26 Apr 2000 10:08:01 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004261708.KAA03066@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: Stephen Hocking , hackers@FreeBSD.ORG Subject: Re: Using the boot loader to set maximum memory size? In-reply-to: Your message of "Wed, 26 Apr 2000 09:26:08 PDT." <20000426092607.L9754@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Apr 2000 10:08:01 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * Stephen Hocking [000426 09:23] wrote: > > Is there any chance of extending the loader so that it can set the memory > > size, rather than hard coding it into the kernel config file? This would be > > quite useful for testing things which like a large amount of memory set aside > > exclusively for hardware's use (I'm thinking of Utah-GLX's DMA buffers for > > G400 cards here). > > Use the undocumented hw.physmem variable in the loader. There isn't an "undocumented hw.physmem" variable, there's only a "documented hw.physmem" variable. -- \\ 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