aboutsummaryrefslogtreecommitdiffstats
path: root/satamv.c
diff options
context:
space:
mode:
authorDaniel Verkamp <dverkamp@chromium.org>2020-10-12 12:55:56 -0700
committerEdward O'Callaghan <quasisec@chromium.org>2020-10-14 10:13:23 +0000
commitca2e3bce02beadc8a2d498fbecf399ae815ebbfc (patch)
tree166f128095d2903ae1995f065d954f3a648993c5 /satamv.c
parent8a99a6e210edfb037571bdc5019ca3b224012c03 (diff)
downloadflashrom-ca2e3bce02beadc8a2d498fbecf399ae815ebbfc.tar.gz
flashrom-ca2e3bce02beadc8a2d498fbecf399ae815ebbfc.tar.bz2
flashrom-ca2e3bce02beadc8a2d498fbecf399ae815ebbfc.zip
pcidev.c: populate IDs with pci_fill_info()
With pciutils 3.7.0, flashrom is unable to match any PCI devices by vendor/device ID because the vendor_id and device_id fields of struct pci_dev are not filled in. Call pci_fill_info() to request these identifiers before trying to match them against the supported device list. The pciutils ChangeLog for 3.7.0 mentions that the documentation and back-end behavior for pci_fill_info() was updated; it seems that a call to pci_fill_info() was always intended to be required, but some backends (such as the sysfs one used on Linux) would fill the identifier fields even when not requested by the user. The pci_fill_info() function and the PCI_FILL_IDENT flag have been available for all versions of pciutils since at least 2.0 from 1999, so it should be safe to add without any version checks. With this change, reading/writing a nicintel_spi boot ROM is successful. Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Change-Id: Ia011d4d801f8a54160e45a70b14b740e6dcc00ef Reviewed-on: https://review.coreboot.org/c/flashrom/+/46310 Reviewed-by: Angel Pons <th3fanbus@gmail.com> Reviewed-by: Nico Huber <nico.h@gmx.de> Reviewed-by: Edward O'Callaghan <quasisec@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'satamv.c')
0 files changed, 0 insertions, 0 deletions