[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 3/6] versatile_pci: user PCIHostState instead of
From: |
Paul Brook |
Subject: |
Re: [Qemu-devel] [PATCH 3/6] versatile_pci: user PCIHostState instead of PCIBus |
Date: |
Wed, 13 Jan 2010 13:02:50 +0000 |
User-agent: |
KMail/1.12.4 (Linux/2.6.32-trunk-amd64; KDE/4.3.4; x86_64; ; ) |
On Tuesday 12 January 2010, Isaku Yamahata wrote:
> To use pci host framework, use PCIHostState instead of PCIBus in
> PCIVPBState.
No.
pci_host.[ch] provides very specific functionality, it is not a generic PCI
host device. Specifically it provides indirect access to PCI config space via
a memory mapped {address,data} pair. The versatile PCI host exposes PCI config
space directly, so should not be using this code.
If you want a generic framework for PCI hosts then you need to use something
else. If nothing else, assuming that a PCI host bridge is always is SysBus
device is wrong.
Paul
Re: [Qemu-devel] [PATCH 6/6] pci host: make pci_data_{write, read}() get PCIConfigAddress., Alexander Graf, 2010/01/12
[Qemu-devel] [PATCH 4/6] pci_host: remove code duplication in pci_host_template.h, Isaku Yamahata, 2010/01/12
[Qemu-devel] [PATCH 2/6] sh_pci: s/sh_pci_data_write/sh_pci_mem_write/g for consistency., Isaku Yamahata, 2010/01/12
[Qemu-devel] [PATCH 1/6] sh_pci: use PCIHostState instead of PCIBus., Isaku Yamahata, 2010/01/12
[Qemu-devel] [PATCH 3/6] versatile_pci: user PCIHostState instead of PCIBus, Isaku Yamahata, 2010/01/12
- Re: [Qemu-devel] [PATCH 3/6] versatile_pci: user PCIHostState instead of PCIBus,
Paul Brook <=
[Qemu-devel] Re: [PATCH 0/6] pci: pci_data_{write, read}() clean up, Michael S. Tsirkin, 2010/01/12