On Tue, 18 Jan 2000, Matthew N. Dodd wrote:
> On Wed, 19 Jan 2000, Poul-Henning Kamp wrote:
> > fxp0: <Intel EtherExpress Pro 10/100B Ethernet> 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.
I did some hacks a while ago on a tool which could be called "devinfo". It
simply traversed the dev/bus tree and displayed tons of info about each
node.
Perhaps something like that could be useful instead of full-blown FS?
Andrzej Bialecki
// <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com)
// -------------------------------------------------------------------
// ------ FreeBSD: The Power to Serve. http://www.freebsd.org --------
// --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ----
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
