From owner-freebsd-current Tue Nov 2 21:45:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 3DEB81504B for ; Tue, 2 Nov 1999 21:45:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA02461; Tue, 2 Nov 1999 21:35:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030535.VAA02461@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: peter.jeremy@Alcatel.com.au Cc: current@FreeBSD.ORG Subject: probe code (was Re: diskless boot roadmap) In-reply-to: Your message of "Wed, 03 Nov 1999 16:36:39 +1100." <99Nov3.163119est.40376@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 21:35:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Initialisation code in the permanently resident kernel is basically > just wasting physical RAM. The less of it there is, the better. > How much of the probe code can we move into userland? Actually, with PnP architectures becoming the norm, probe code basically goes away, so the whole point is pretty moot. Attach code is somewhat bulkier, but you need to bear in mind that it's needed for devices that arrive after boot time. Attach code is typically far too closely tied to the operational code to separate it at all. -- \\ 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-current" in the body of the message