On Sun, Sep 30, 2007 at 03:34:57PM -0700, Marcel Moolenaar wrote: > On Sep 30, 2007, at 3:17 PM, Marius Strobl wrote: > > >>Where it would previously succeed, I now get .. > >> > >>toshi# pciconf -wb pci0:30:0 0x1a 8 > >>pciconf: ioctl(PCIOCWRITE): Operation not supported by device > >> > > > >As mentioned the format of the location strings has changed, > >you probably need to use pci0:0:30:0. > > If compatibility is a concern, we may be able to make the parsing > a bit more smart without too much complexity. We can count the > number of colons for exampl,e and assume missing elements are 0. > So, if one enters pci1:2:3, the domain will be 0. If one enters > pci4:5, both the domain and bus will be 0, etc. > > Just a thought... > Unfortunately, for pciconf(8) the function is already optional so pci1:2:3 would be ambiguous. Originally my plan was to strip the 'pci' for strings specifing a location including a domain and keep the pcib:s:f format for backwards compatibility, but John was against this as he wants the format to be uniform with the strings used for a hints feature he is working on and which in turn relies on the 'pci' part. MariusReceived on Sun Sep 30 2007 - 21:16:22 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:18 UTC