Displaying 6 results from an estimated 6 matches for "pci_cap_id_vendor".
2015 Jan 21
2
[pciutils patch] add virtio vendor capability support
virtio uses vendor-specific capabilities to specify the location of
the virtio register ranges. The specification can be found here:
http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004
This patch adds support for decoding these capabilities to lspci.
Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>
---
Makefile | 2 +-
ls-caps-vendor.c | 59
2015 Jan 21
2
[pciutils patch] add virtio vendor capability support
virtio uses vendor-specific capabilities to specify the location of
the virtio register ranges. The specification can be found here:
http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004
This patch adds support for decoding these capabilities to lspci.
Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>
---
Makefile | 2 +-
ls-caps-vendor.c | 59
2015 Jan 21
0
[pciutils patch] add virtio vendor capability support
...who knows what
happens in the future ...
> (3) Moving code related to vendor-defined caps to a separate file sounds
> good, but I think we should push the boundary a bit further: let the
> main switch in ls-caps.c call a function from ls-caps-vendor.c as soon
> as it finds PCI_CAP_ID_VENDOR, leaving all decisions based on
> vendor/device ID to this function.
Makes sense indeed, will do.
cheers,
Gerd
2015 Jan 21
0
[pciutils patch] add virtio vendor capability support
...who knows what
happens in the future ...
> (3) Moving code related to vendor-defined caps to a separate file sounds
> good, but I think we should push the boundary a bit further: let the
> main switch in ls-caps.c call a function from ls-caps-vendor.c as soon
> as it finds PCI_CAP_ID_VENDOR, leaving all decisions based on
> vendor/device ID to this function.
Makes sense indeed, will do.
cheers,
Gerd
2015 Jan 21
1
[pciutils patch] add virtio vendor capability support
...but the comment nearby refers to a range of device IDs only.
(3) Moving code related to vendor-defined caps to a separate file sounds
good, but I think we should push the boundary a bit further: let the
main switch in ls-caps.c call a function from ls-caps-vendor.c as soon
as it finds PCI_CAP_ID_VENDOR, leaving all decisions based on
vendor/device ID to this function.
Could you please fix these and resubmit?
Have a nice fortnight
--
Martin `MJ' Mares <mj at ucw.cz> http://mj.ucw.cz/
Faculty of Math and Physics, Charles University, Prague, Czech Rep....
2015 Jan 21
1
[pciutils patch] add virtio vendor capability support
...but the comment nearby refers to a range of device IDs only.
(3) Moving code related to vendor-defined caps to a separate file sounds
good, but I think we should push the boundary a bit further: let the
main switch in ls-caps.c call a function from ls-caps-vendor.c as soon
as it finds PCI_CAP_ID_VENDOR, leaving all decisions based on
vendor/device ID to this function.
Could you please fix these and resubmit?
Have a nice fortnight
--
Martin `MJ' Mares <mj at ucw.cz> http://mj.ucw.cz/
Faculty of Math and Physics, Charles University, Prague, Czech Rep....