Messages in this thread | | | Subject | Re: /proc/pci design idea | Date | Mon, 15 Sep 1997 09:17:10 +0800 | From | Stephen Williams <> |
| |
paubert@iram.es said: > Would it be possible to make the directory structure more dynamic ? > I'm aware it may be quite complex :-(
None of the existing Linux PCI support that I ran into rescans the bus. If that is worked out, I can arranged for directory entries to be changed as new devices appear.
paubert@iram.es said: > Does anybody know what configuration space header type 2 layout is ?
This sort of thing is exactly why I decided that pretty-printing in the kernel is a bad idea. Haven't we all noticed by now that /proc/pci never handled bridges (which have a different layout.)
amorsen@sscnet.com said: > I'll miss /proc/pci. I can live with that, of course, but I'll miss > it. I love being able to use the linux kernel for diagnostics.
All the capabilities of /proc/pci live on, though a usr mode program is helpful for the convenience of us humans.
jxfaultl@bechtel.com said: > I would make only one comment; keep the text of the vendors and > devices in an external ASCII file, such as /etc/pcitab for easy > updates. I would guess the program to print the info should > ultimately wind up in the util-linux package.
This all sounds reasonable. I have also considered keeping it in a dbm table and bundling programs to add/delete/print. Text file may be fine for this point, though.
| |