From owner-freebsd-current Wed Apr 25 20: 1:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 3818537B422 for ; Wed, 25 Apr 2001 20:01:27 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id XAA15921; Wed, 25 Apr 2001 23:01:23 -0400 (EDT) (envelope-from wollman) Date: Wed, 25 Apr 2001 23:01:23 -0400 (EDT) From: Garrett Wollman Message-Id: <200104260301.XAA15921@khavrinen.lcs.mit.edu> To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: Boot messages In-Reply-To: <200104252258.f3PMvu827905@harmony.village.org> References: <20010424231959.933A63E2B@bazooka.unixfreak.org> <200104252258.f3PMvu827905@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Actually, it is a bug. The drivers in the tree should grok these pnp > ids. Actually, no, it is not a bug. The FreeBSD drivers for these devices manage their resources differently from the way the Windows drivers do, and the result is not unexpected if you look closely at the dump in verbose mode. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message