From owner-freebsd-current  Tue Jun 13 11:41:43 2000
Delivered-To: freebsd-current@freebsd.org
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
	by hub.freebsd.org (Postfix) with ESMTP
	id A622237BC3F; Tue, 13 Jun 2000 11:41:37 -0700 (PDT)
	(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
	by lor.watermarkgroup.com (8.10.1/8.10.1) id e5DHrdi06492;
	Tue, 13 Jun 2000 13:53:39 -0400 (EDT)
Date: Tue, 13 Jun 2000 13:53:39 -0400 (EDT)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <200006131753.e5DHrdi06492@lor.watermarkgroup.com>
To: msmith@FreeBSD.ORG
Subject: Re: VMware detection code in boot loader
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > a larger issue. It is not the loader's job to detect the underlying
> > hardware configuration.
> 
> Actually, in a broad fashion, it _is_.  This is why the loader 
> understands PCI and PnP, for example.
> 
Why do we want to do that? Are we going to offload device probe routines to
the loader? I thought the loader only needs to understand bootable devices,
and it's the kernel's responsibility to handle the rest.

-lq


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message