From owner-freebsd-current  Sat Jun 10  6:31:49 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 9749F37B71B; Sat, 10 Jun 2000 06:31:41 -0700 (PDT)
	(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
	by lor.watermarkgroup.com (8.10.1/8.10.1) id e5ADVe205943;
	Sat, 10 Jun 2000 09:31:40 -0400 (EDT)
Date: Sat, 10 Jun 2000 09:31:40 -0400 (EDT)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <200006101331.e5ADVe205943@lor.watermarkgroup.com>
To: dcs@newsguy.com
Subject: Re: VMware detection code in boot loader
Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> We have inb and outb. Can't vmware be written in Forth? If inl cannot be
> replaced with inb, I'd rather add inl than vmware.
> 
But we can't set registers to specific values before inb/outb, which also
means our inb/outb are quite useless in making BIOS calls.

> IMHO, it would be better to add
> 
> exec="include /boot/vmware.4th"
> 
> to the end of your /boot/loader.conf, and either execute vmware-conf
> from there or script the whole thing:
> 
> s" arch-i386" environment? [if]
> 	\ Get vmware version, magic
> 	0x564d868 ( VMware magic ) = [if]
> 		.( VMware version ) . cr
> 		.( Loading /boot/vmware.conf...) cr
> 		s" /boot/vmware.conf" read-conf
> 	[else]
> 		drop
> 	[then]
> [then]
> 
> Either way, no changes to /boot/loader.rc would be required.
> 
This looks much better, I didn't know we could tell the loader to execute a
script in loader.conf.

> -- 
> Daniel C. Sobral			(8-DCS)
> 
> dcs@newsguy.com
> dcs@freebsd.org
> capo@yet.another.bsdconspiracy.org
> 
> 	Hmmm - I have to go check this. My reality assumptions are shattered.
> 

-lq


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