From owner-freebsd-current Tue Jan 18 15:36:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id E0A5414DB1; Tue, 18 Jan 2000 15:36:17 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id SAA73441; Tue, 18 Jan 2000 18:35:27 -0500 (EST) Date: Tue, 18 Jan 2000 18:35:26 -0500 (EST) From: "Matthew N. Dodd" To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: boot messages for pci devices... In-Reply-To: <31733.948238089@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Poul-Henning Kamp wrote: > 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 ? Its consistant, but I need to unify all the resource printing stuff since theres about 5 different ways that are being used to print the stuff right now. I'll do this after 4.0R. > 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. Humm... Thats possible. There was talk a while ago about making multiple levels of verbosity in the bootup messages. I'll explore this when I fix the line wrapping issues. It would really be nice if we could have busfs; this would make it much easier to allow access to this sort of information. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message