From owner-freebsd-current Wed Aug 11 22:29:35 1999 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 4A58314E07 for ; Wed, 11 Aug 1999 22:29:30 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id BAA12604; Thu, 12 Aug 1999 01:29:33 -0400 (EDT) Date: Thu, 12 Aug 1999 01:29:32 -0400 (EDT) From: "Matthew N. Dodd" To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: it's time... In-Reply-To: <199908120514.XAA02076@harmony.village.org> 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, 11 Aug 1999, Warner Losh wrote: > In message "Matthew N. Dodd" writes: > : check out eisa_reg_print() and eisa_print_child() in > : sys/i386/eisa/eisaconf.c > : > : Sanity in output is a good thing. > > Agreed. I like what I see there. Maybe it is time to hoist something > like that into bus_subr.c Lets define exactly what we want before we start our charge. What should be printed? device ID attachment point resource reservation device additional When should it be printed? bootverbose levels? How should it printed? ???N: on ???N ... or... Since we've got things partway tied up with new_bus, maybe we should complete the job, and define a device method for printing out the device additional information so it can be dispatched from a single place. How are we going to enforce the use of this 'pretty printer'? Should we embed this logic in device_printf()? This would be practical if our goal were not only impose order on the probe/attach messages but also anything a driver printed (nothing more annoying that stray error messages for which the issuing device is unknown.) I'm not sure this is our goal at this time? Will we ever have such a goal? I see our goal as follows. 1. one unified format for devce probe/attach ammouncments. 2. the ability to control the amount of information printed during the device probe/attach. Anyhow, just trying to stir up some ideas here; please don't take any of my statements as an indication of intended course. I really don't have any good answers at this point and would like to hear the opinions of others. -- | 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