Change Details

I have tested the following formats: text, xml, html, json. Text output with no --libxo option or with "--libxo test" was unchanged. Other output formats (xml, json) should be easy to parse (Q: are identifiers sensible? structure?). XML and JSON output of VPD data should be tested - I do not have a suitable system and no good specification of the fields. Test commands: pciconf --libxo %format% -l pciconf --libxo %format% -lb pciconf --libxo %format% -lc pciconf --libxo %format% -le pciconf --libxo %format% -lv pciconf --libxo %format% -lV pciconf --libxo %format% -lv %selector% pciconf --libxo %format% -a %selector% pciconf --libxo %format% -r %selector% In all cases except -a the selector should be the bus-id of an existing device. For -a both existing and non-existing devices should be checked, as well as devices matching "none*".

This version of pciconf should generate 100% identical output, except when one of the structured XO formats is requested. I have tested the following formats: text, xml, html, json. Text output with no --libxo option or with "--libxo test" was unchanged for all output generated on my test system, but I cannot generate all possible output, thus coverage is not good enough. Test commands: pciconf --libxo %format% -lbcevV pciconf --libxo %format% -lbcevV %selector% pciconf --libxo %format% -a %selector% pciconf --libxo %format% -r %selector% In all cases except -a the selector should be the bus-id of an existing device or the device name (e.g. "re0"). For -a both existing and non-existing devices should be checked, as well as devices matching "none*" in "pciconf -l" output.

This version of pciconf should generate 100% identical output, except when one of the structured XO formats is requested. I have tested the following formats: text, xml, html, json. Text output with no --libxo option or with "--libxo test" was unchanged. Other for all output formats (xmlgenerated on my test system, json) should be easy to parse (Q: are identifiers sensible?but I cannot generate all possible output, structure?). XML and JSON output of VPD data should be tested - I do not have a suitable system and no good specification of the fieldsthus coverage is not good enough. Test commands: pciconf --libxo %format% -lbcevV pciconf --libxo %format% -lbcevV %selector% pciconf --libxo %format% -lc pciconf --libxo %format% -le pciconf --libxo %format% -lv pciconf --libxo %format% -lV pciconf --libxo %format% -lv %selector% pciconf --libxo %format% -a %selector% pciconf --libxo %format% -r %selector% In all cases except -a the selector should be the bus-id of an existing device or the device name (e.g. "re0"). For -a both existing and non-existing devices should be checked, as well as devices matching "none*" in "pciconf -l" output.