From owner-freebsd-current Tue Jan 18 15:31:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0E21214C85 for ; Tue, 18 Jan 2000 15:31:33 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id AAA31735 for ; Wed, 19 Jan 2000 00:28:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: boot messages for pci devices... From: Poul-Henning Kamp Date: Wed, 19 Jan 2000 00:28:09 +0100 Message-ID: <31733.948238089@critter.freebsd.dk> 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 ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message