From owner-freebsd-current Tue Jan 18 16: 6:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 9FE12150E3 for ; Tue, 18 Jan 2000 16:06:54 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id QAA27689 for ; Tue, 18 Jan 2000 16:02:36 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001190002.QAA27689@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-reply-to: Your message of "Wed, 19 Jan 2000 00:28:09 +0100." <31733.948238089@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jan 2000 16:02:36 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > fxp0: port 0xc400-0xc43f mem 0xefe00000-0xefefffff,0xeffff000-0xefffffff irq 9 at device 14.0 on pci0 > > Is this level of verbosity really helping anybody ? > > I thought we printed out the port/mem stuff for ISA because it is > usually jumpered by the admin, but for dynamic allocation busses/devices > I think this should be "bootverbose" material. > > Or maybe we should always make the resource allocations bootverbose stuff > now ? > I think that the pci info should be displayed onlly in verbose mode . Some of the pci devices specially the newer graphic cards have tons of memory map registers and it is of virtually no use to users. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message