Home
last modified time | relevance | path

Searched refs:PCI (Results 1 – 25 of 139) sorted by relevance

123456

/qemu/docs/
A Dpcie.txt27 PCI/PCI Express slot.
54 (3) PCI Express to PCI Bridge (pcie-pci-bridge), for starting legacy PCI
71 PCI Express Root Ports and PCI Express to PCI bridges can be
145 PCI Express to PCI Bridge until is full and then plug a new PCI-PCI Bridge...
155 | PCI-PCI Bridge | | PCI-PCI Bridge |
164 2.3.2 Plugging a PCI device into a PCI-PCI Bridge:
169 the PCI Bridge/PCI Express to PCI Bridge.
227 (3) PCI Express to PCI Bridges
233 PCI devices can be hot-plugged into PCI Express to PCI and PCI-PCI Bridges.
244 or more empty PCI-PCI Bridges to the PCI Express to PCI Bridge.
[all …]
A Dpcie_pci_bridge.txt1 Generic PCI Express to PCI Bridge
6 PCIE-to-PCI bridge is a new method for legacy PCI
9 Previously Intel DMI-to-PCI bridge was used for this purpose.
12 PCIE-to-PCI bridge should now be used for any legacy PCI device usage
13 with PCI Express machine.
15 This generic PCIE-PCI bridge is a cross-platform device,
17 see 'PCIE-PCI bridge hot-plug' section),
21 Hot-plug of legacy PCI devices into the bridge
25 PCIE-PCI bridge hot-plug
112 The PCIE-PCI bridge is based on PCI-PCI bridge, but also accumulates PCI Express
[all …]
A Dpci_expander_bridge.txt1 PCI EXPANDER BRIDGE (PXB)
6 PXB is a "light-weight" host bridge in the same PCI domain
8 the main host bridge to support multiple PCI root buses.
12 As opposed to PCI-2-PCI bridge's secondary bus, PXB's bus
46 The host bridge allows to register and query the PXB's PCI root bus in QEMU.
48 …It is a regular PCI Device that resides on the piix host-bridge bus and its bus uses the same PCI …
49 …However, the bus behind is exposed through ACPI as a primary PCI bus and starts a new PCI hierarch…
51 PCI-2-PCI bridge. The _PRT follows the i440fx model.
57 the PCI address space.
A Dqemupciserial.inf29 %QEMU-PCI_SERIAL_1_PORT%=ComPort_inst1, PCI\VEN_1B36&DEV_0002
30 %QEMU-PCI_SERIAL_2_PORT%=ComPort_inst2, PCI\VEN_1B36&DEV_0003
31 %QEMU-PCI_SERIAL_4_PORT%=ComPort_inst4, PCI\VEN_1B36&DEV_0004
34 %QEMU-PCI_SERIAL_1_PORT%=ComPort_inst1, PCI\VEN_1B36&DEV_0002
35 %QEMU-PCI_SERIAL_2_PORT%=ComPort_inst2, PCI\VEN_1B36&DEV_0003
36 %QEMU-PCI_SERIAL_4_PORT%=ComPort_inst4, PCI\VEN_1B36&DEV_0004
100 QEMU-PCI_SERIAL_1_PORT="1x QEMU PCI Serial Card"
101 QEMU-PCI_SERIAL_2_PORT="2x QEMU PCI Serial Card"
102 QEMU-PCI_SERIAL_4_PORT="4x QEMU PCI Serial Card"
A Dqdev-device-use.txt14 PCI addr %x.%x (dev.fn, .fn optional)
95 As for all PCI devices, you can add bus=PCI-BUS,addr=DEVFN to
96 control the PCI device address.
117 This lets you control PCI device class and MSI-X vectors.
122 As for all PCI devices, you can add bus=PCI-BUS,addr=DEVFN to
260 For PCI devices, you can add bus=PCI-BUS,addr=DEVFN to control the PCI
293 As for all PCI devices, you can add bus=PCI-BUS,addr=DEVFN to control
294 the PCI device address.
330 For PCI devices, you can add bus=PCI-BUS,addr=DEVFN to control the PCI
359 The new way is -device DEVNAME. For PCI devices, you can add
[all …]
A Dbypass-iommu.txt13 PCI host bridges have a bypass_iommu property. This property is used to
14 determine whether the devices attached on the PCI host bridge will bypass
30 (1) PCI expander bridge
75 Add bypass iommu property check of PCI Host and do not get iommu address
78 We traverse all PCI root bus and get bus number ranges, then build explicit
81 To support Intel iommu, we traverse all PCI host bridge and get information
84 when traverse the PCI hsot bridge.
/qemu/hw/pci-host/
A DKconfig11 select PCI
15 select PCI
19 select PCI
23 select PCI
28 select PCI
33 select PCI
37 select PCI
41 select PCI
46 select PCI
68 select PCI
[all …]
/qemu/docs/specs/
A Dpci-ids.rst2 PCI IDs for QEMU
61 PCI devices (other than virtio):
64 PCI-PCI bridge
72 PCI test device (:doc:`pci-testdev`)
74 PCI Rocker Ethernet switch device
80 PCI Expander Bridge (``-device pxb``)
82 PCI-PCI bridge (multiseat)
88 PCI xhci usb host adapter
96 PCI PVPanic device (``-device pvpanic-pci``)
100 PCI UFS device (``-device ufs``)
[all …]
A Dpci-serial.rst2 QEMU PCI serial devices
5 QEMU implements some PCI serial devices which are simple PCI
18 PCI ID:
20 PCI Region 0:
31 PCI ID:
33 PCI Region 0:
A Dacpi_pci_hotplug.rst1 QEMU<->ACPI BIOS PCI hotplug interface
4 QEMU supports PCI hotplug via ACPI, for PCI bus 0. This document
10 Generic ACPI GPE block. Bit 1 (GPE.1) used to notify PCI hotplug/eject
13 PCI slot injection notification pending (IO port 0xae00-0xae03, 4-byte access)
21 PCI slot removal notification (IO port 0xae04-0xae07, 4-byte access)
29 PCI device eject (IO port 0xae08-0xae0b, 4-byte access)
44 PCI removability status (IO port 0xae0c-0xae0f, 4-byte access)
A Dstandard-vga.rst19 PCI spec
24 PCI ID
27 PCI Region 0
31 PCI Region 1
34 PCI Region 2
37 PCI ROM Region
A Dedu.rst15 The devices behaves very similar to the PCI bridge present in the COMBO6 cards
16 developed under the Liberouter wings. Both PCI device ID and PCI space is
28 PCI specs
31 PCI ID:
34 PCI Region 0:
117 PCI address ``addr``:
A Driscv-iommu.rst9 The emulation includes a PCI reference device, riscv-iommu-pci, that QEMU
17 "Integrating an IOMMU as a PCIe device" of `iommu1.0`_: a PCI device with base
21 so it uses a generic default PCI ID given by QEMU: 1b36:0014.
29 This will add a RISC-V IOMMU PCI device in the board following any additional
30 PCI parameters (like PCI bus address). The behavior of the RISC-V IOMMU is
69 a Rivos PCI IOMMU by setting 'vendor-id' and 'device-id':
/qemu/qapi/
A Dpci.json9 # = PCI
15 # A PCI device memory region
28 # Information about a PCI device I/O region.
82 # Information about a PCI Bridge device
96 # Information about the Class of a PCI device
111 # Information about the Id of a PCI device
113 # @device: the PCI device id
115 # @vendor: the PCI vendor id
130 # Information about a PCI device
140 # @id: the PCI device id
[all …]
A Dcommon.json74 # An enumeration of options for specifying a PCI BAR
78 # @auto: The PCI BAR for the feature is automatically selected
80 # @bar0: PCI BAR0 is used for the feature
82 # @bar1: PCI BAR1 is used for the feature
84 # @bar2: PCI BAR2 is used for the feature
86 # @bar3: PCI BAR3 is used for the feature
88 # @bar4: PCI BAR4 is used for the feature
90 # @bar5: PCI BAR5 is used for the feature
/qemu/hw/net/
A DKconfig10 depends on PCI
16 depends on PCI
22 depends on PCI
31 depends on PCI
40 depends on PCI
55 depends on PCI
60 depends on PCI
115 depends on PCI
135 depends on PCI && MSI_NONBROKEN
148 depends on PCI && CAN_SJA1000
[all …]
/qemu/docs/system/s390x/
A Dpcidevices.rst1 PCI devices on s390x
4 PCI devices on s390x work differently than on other architectures and need to
7 Every PCI device is linked with an additional ``zpci`` device.
10 PCI configuration.
12 For example, in order to pass a PCI device ``0000:00:00.0`` through to the
19 Here, the zpci device is joined with the PCI device via the ``target`` property.
22 other PCI implementations. Topology information is not available on s390x, and
29 In case of Linux, ``uid`` will be used in the ``domain`` part of the PCI
/qemu/hw/scsi/
A DKconfig7 depends on PCI
13 depends on PCI
19 depends on PCI
25 depends on PCI
35 depends on PCI
63 # Only PCI devices are provided for now
/qemu/docs/config/
A Dq35-emulated.cfg22 # plus a small selection of core PCI devices and
26 # The core PCI devices show up in the guest as:
41 # 00:1c.* PCI bridge (PCI Express Root Ports)
43 # 00:1e.0 PCI bridge (legacy PCI bridge)
72 # PCI bridge (PCI Express Root Ports)
75 # We add four PCI Express Root Ports, all sharing the same
76 # slot on the PCI Express Root Bus. These ports support
112 # PCI bridge (legacy PCI bridge)
116 # for legacy PCI devices. PCI Express devices should be
279 # The sound card is a legacy PCI device that is plugged
[all …]
A Dq35-virtio-graphical.cfg22 # plus a small selection of core PCI devices and
26 # The core PCI devices show up in the guest as:
38 # 00.1c.* PCI bridge (PCI Express Root Ports)
66 # PCI bridge (PCI Express Root Ports)
69 # We create eight PCI Express Root Ports, and we plug them
214 # We plug the QXL video card directly into the PCI Express
215 # Root Bus as it is a legacy PCI device; this way, we can
216 # reduce the number of PCI Express controllers in the
238 # Like the video card, the sound card is a legacy PCI
239 # device and as such can be plugged directly into the PCI
/qemu/hw/display/
A DKconfig15 depends on PCI
43 depends on PCI
59 depends on PCI
65 depends on PCI
94 depends on SPICE && PCI && PIXMAN
126 depends on PCI
/qemu/docs/system/arm/
A Dversatile.rst18 - PCI host bridge. Note the emulated PCI bridge only provides access
19 to PCI memory space. It does not provide access to PCI IO space. This
24 - PCI OHCI USB controller.
26 - LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
/qemu/docs/system/
A Dtarget-i386-desc.rst.inc3 - i440FX host PCI bridge and PIIX3 PCI to ISA bridge
5 - Cirrus CLGD 5446 PCI VGA card or dummy VGA card with Bochs VESA
10 - 2 PCI IDE interfaces with hard disk and CD-ROM support
14 - PCI and ISA network adapters
36 - PCI UHCI, OHCI, EHCI or XHCI USB controller and a virtual USB-1.1
/qemu/docs/system/devices/
A Dcxl.rst32 - Many other PCI express defined interfaces..
51 via means such as PCI memory reads and writes to BARs.
72 more like PCI Express, with fully specified discoverability
102 as CXL Component Registers in PCI BARs.
117 and associated component register access via PCI bars.
179 | PCI/CXL Root Bus 0c | | PCI/CXL Root Bus 0d |
190 | PCI topology | | PCI topology| | PCI topo | | PCI topo |
201 | from host PA | | PCI 0e:00.0 | | PCI df:00.0| | PCI e0:00.0 |
264 | PCI/CXL Root Bus 0c | | PCI/CXL Root Bus 0d |
274 | PCI topology |
[all …]
/qemu/hw/audio/
A DKconfig9 depends on PCI
14 depends on PCI
34 depends on PCI

Completed in 657 milliseconds

123456