Lines Matching +full:fpga +full:- +full:based

31 ----------------------
35 based devices.
38 -----------------------------------------
40 The current implementation is limited to PCI and PCIe based carrier devices
44 - Multi-resource MCB devices like the VME Controller or M-Module carrier.
45 - MCB devices that need another MCB device, like SRAM for a DMA Controller's
47 - A per-carrier IRQ domain for carrier devices that have one (or more) IRQs
48   per MCB device like PCIe based carriers with MSI or MSI-X support.
55 - The MEN Chameleon Bus itself,
56 - drivers for MCB Carrier Devices and
57 - the parser for the Chameleon table.
60 -----------------
63 called Chameleon FPGA device found on some hardware produced my MEN Mikro
64 Elektronik GmbH. These devices are multi-function devices implemented in a
65 single FPGA and usually attached via some sort of PCI or PCIe link. Each
66 FPGA contains a header section describing the content of the FPGA. The
68 BAR, size in the FPGA, interrupt number and some other properties currently
72 ---------------
75 Chameleon FPGA is attached to. Some IP Core drivers may need to interact with
84 ------
102 ----------------
110 ----
113 MCB bus. If a carrier device driver implements the ->get_irq() callback
122 --------------------
125 device ids which identify the IP Core inside the FPGA. The driver structure
137 		.name = "foo-bar",
146 ---------------------
156 -----------------------
179 ---------
181 To make use of the kernel's DMA-API's function, you will need to use the
183 pointer (->dma_dev) to the carrier's device for DMA purposes::
185         ret = dma_set_mask_and_coherent(&mdev->dma_dev, DMA_BIT_MASK(dma_bits));