On 01/14/2010 05:26 PM, Ryan C. Underwood wrote:
On Thu, Jan 14, 2010 at 03:59:53PM +0200, Avi Kivity wrote:
>
> >Also, just for further complication, the Ricoh chip does not support
> >MSI and shares an IRQ on the system board with the USB host controller.
> >I have rebound the USB host controller to pci-stub, but I'm not sure if
> >that totally takes care of the IRQ-sharing-without-MSI issue.
>
> Can you post lspci -vv output for that card? If it is pci 2.3
> compliant we might be able to handle the sharing.
It claims to be PCI 3.0 compliant. But I don't see any mention MSI
anywhere in the specification:
http://www.aeneas.com.cn/PDF/Ricoh/2005/R5C832E1%5B1%5D.00.pdf
Attached is lspci -vv, thanks.
08:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) (prog-if 10)
Subsystem: Hewlett-Packard Company Device 30cd
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium>TAbort-<TAbort-<MAbort->SERR-<PERR- INTx-
Latency: 64 (500ns min, 1000ns max)
Interrupt: pin A routed to IRQ 16
Region 0: [virtual] Memory at f4400000 (32-bit, non-prefetchable) [size=2K]
Capabilities:<access denied>
Kernel driver in use: pci-stub
Kernel modules: firewire-ohci, ohci1394
Michael, I think 'DisINTx-' means the device is not PCI 2.3 compliant?
08:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
Subsystem: Hewlett-Packard Company Device 30cd
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium>TAbort-<TAbort-<MAbort->SERR-<PERR- INTx-
Latency: 248, Cache Line Size: 1020 bytes
Interrupt: pin B routed to IRQ 10
Region 0: Memory at f4401400 (32-bit, non-prefetchable) [size=256]
Capabilities:<access denied>
Kernel driver in use: pci-stub
But another function has this feature?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
