From owner-freebsd-emulation Thu Jun 22 12:24:57 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mass.osd.bsdi.com (dhcp183.conference.usenix.org [209.179.127.183]) by hub.freebsd.org (Postfix) with ESMTP id BA5FA37BC4C; Thu, 22 Jun 2000 12:24:52 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id MAA00940; Thu, 22 Jun 2000 12:30:19 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200006221930.MAA00940@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: VMware detection code in boot loader In-reply-to: Your message of "Wed, 21 Jun 2000 14:02:26 MDT." <200006212002.OAA83024@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Jun 2000 12:30:19 -0700 From: Mike Smith Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In message <200006131710.KAA22395@mass.cdrom.com> Mike Smith writes: > : > 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. > > How hard would it be to add usb and pccard support? Very hard. There's no standardised firmware interface to either of these, so we would have to use "real" drivers. As far as the loader is concerned, though, neither of these are on the boot path, so we can typically wait until the kernel's up and we can use some "real real" drivers. 8) -- \\ 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-emulation" in the body of the message