Date: Mon, 16 Jun 2003 23:39:08 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: gurney_j@efn.org Cc: arch@freebsd.org Subject: Re: make /dev/pci really readable Message-ID: <20030616.233908.94890442.imp@bsdimp.com> In-Reply-To: <20030617053456.GG73854@funkthat.com> References: <20030617050905.GE73854@funkthat.com> <20030616.231258.116352275.imp@bsdimp.com> <20030617053456.GG73854@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20030617053456.GG73854@funkthat.com>
John-Mark Gurney <gurney_j@efn.org> writes:
: You can take a look at it if you want (I'll send you my patchse
: shortly.). Shouldn't take but about 5-10 minutes of your time. It's
: a VERY simple interface/code.
Actually, looks like the interactions with others have done a great
job of doing that.
: > : > You can get the same information that pciconf -l does by going through
: > : > the alternative interface of devinfo.
: > :
: > : So, I hear you proposing to remove pciconf and the /dev/pci interface?
: >
: > Not really. I'm saying that we should beef up devinfo interface so
: > that it can get PNP information from more databases that just the PCI
: > one. pciconf is the wrong place for -v to be placed. But it was the
: > only place to place it when it was written. Now that other busses
: > have begun to implement pnp info to userland, we should look at a good
: > way to deal.
:
: I agree... devinfo is much beter than pciconf for device information,
: but this whole bit was just started to get one small piece of code
: committed, at least it'll be better while it lasts.
True. It will be a while before devinfo can get the TLC I really want
to give it.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030616.233908.94890442.imp>