Displaying 2 results from an estimated 2 matches for "conf_space_capability_pm".
2007 Jul 08
6
Permissive devices in Xen
Hello,
is there any reason why even permissive devices cannot write some areas in the
PCI config space?
The PCI_COMMAND is handled in special way so that the device is
enabled/disabled properly, am I right?
Why is PCI_INTERRUPT_LINE read from dev->irq and not from the config space?
Why the PCI address bars are handled in very different way? And it seems that
writing these bars is never
2007 Mar 26
3
[PATCH] pciback: restore PCI BARs on D3->D0 transition
...programmed. The patch below adds a call to
pci_restore_bars() as a workaround until we can figure out why the PCI
code doesn''t do this for us. Thanks,
Alex
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
---
diff -r 56caf0e37e6a linux-2.6-xen-sparse/drivers/xen/pciback/conf_space_capability_pm.c
--- a/linux-2.6-xen-sparse/drivers/xen/pciback/conf_space_capability_pm.c Mon Mar 26 10:10:31 2007 -0600
+++ b/linux-2.6-xen-sparse/drivers/xen/pciback/conf_space_capability_pm.c Mon Mar 26 13:13:23 2007 -0600
@@ -33,7 +33,7 @@ static int pm_ctrl_write(struct pci_dev
{
int err;
u16 cur_valu...