From owner-freebsd-current Wed Apr 25 20: 5:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 091A437B423 for ; Wed, 25 Apr 2001 20:05:36 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.2) with ESMTP id f3Q39VL20710; Wed, 25 Apr 2001 20:09:32 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104260309.f3Q39VL20710@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Wollman Cc: Warner Losh , freebsd-current@FreeBSD.ORG Subject: Re: Boot messages In-reply-to: Your message of "Wed, 25 Apr 2001 23:01:23 EDT." <200104260301.XAA15921@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Apr 2001 20:09:31 -0700 From: Mike Smith 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. I'll say this for the seventeenth time, it is a bug; it's in the way that a) hints are handled, and b) the way that the console code currently works. It's also not really dangerous, so most people ignore it. There are much bigger problems to worry about. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message