Home
last modified time | relevance | path

Searched refs:VME (Results 1 – 25 of 506) sorted by relevance

12345678910>>...21

/dports/multimedia/libv4l/linux-5.13-rc2/drivers/vme/bridges/
H A DKconfig2 comment "VME Bridge Drivers"
9 (Universe II) VME bridge chip.
15 If you say Y here you get support for the Tundra TSI148 VME bridge
21 If you say Y here you get support for the fake VME bridge. This
22 provides a virtualised VME Bus for devices with no VME bridge. This
23 is mainly useful for VME development (in the absence of VME
/dports/multimedia/v4l_compat/linux-5.13-rc2/drivers/vme/bridges/
H A DKconfig2 comment "VME Bridge Drivers"
9 (Universe II) VME bridge chip.
15 If you say Y here you get support for the Tundra TSI148 VME bridge
21 If you say Y here you get support for the fake VME bridge. This
22 provides a virtualised VME Bus for devices with no VME bridge. This
23 is mainly useful for VME development (in the absence of VME
/dports/multimedia/v4l-utils/linux-5.13-rc2/drivers/vme/bridges/
H A DKconfig2 comment "VME Bridge Drivers"
9 (Universe II) VME bridge chip.
15 If you say Y here you get support for the Tundra TSI148 VME bridge
21 If you say Y here you get support for the fake VME bridge. This
22 provides a virtualised VME Bus for devices with no VME bridge. This
23 is mainly useful for VME development (in the absence of VME
/dports/multimedia/libv4l/linux-5.13-rc2/Documentation/driver-api/
H A Dvme.rst1 VME Device Drivers
7 As with other subsystems within the Linux kernel, VME device drivers register
57 requesting VME resources.
65 split into the VME address spaces that need to be accessed in 'aspace' and VME
74 and/or MEM-to-VME, though some hardware can support VME-to-VME and MEM-to-MEM
183 source or destination is in an unsupported VME address space.
194 - VME source or destination: :c:func:`vme_dma_vme_attribute`
211 The VME API provides functions to attach and detach callbacks to specific VME
213 specific VME level and status IDs.
236 at a given VME level and VME status ID.
[all …]
/dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/driver-api/
H A Dvme.rst1 VME Device Drivers
7 As with other subsystems within the Linux kernel, VME device drivers register
57 requesting VME resources.
65 split into the VME address spaces that need to be accessed in 'aspace' and VME
74 and/or MEM-to-VME, though some hardware can support VME-to-VME and MEM-to-MEM
183 source or destination is in an unsupported VME address space.
194 - VME source or destination: :c:func:`vme_dma_vme_attribute`
211 The VME API provides functions to attach and detach callbacks to specific VME
213 specific VME level and status IDs.
236 at a given VME level and VME status ID.
[all …]
/dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/driver-api/
H A Dvme.rst1 VME Device Drivers
7 As with other subsystems within the Linux kernel, VME device drivers register
57 requesting VME resources.
65 split into the VME address spaces that need to be accessed in 'aspace' and VME
74 and/or MEM-to-VME, though some hardware can support VME-to-VME and MEM-to-MEM
183 source or destination is in an unsupported VME address space.
194 - VME source or destination: :c:func:`vme_dma_vme_attribute`
211 The VME API provides functions to attach and detach callbacks to specific VME
213 specific VME level and status IDs.
236 at a given VME level and VME status ID.
[all …]
/dports/graphics/fig2sxd/fig2sxd-edae2efd428623ac22aec06bdec572fc45c368f3/examples/
H A Dabort.fig5183 4 1 0 0 0 0 14 0.0000 0 225 1125 44506 26756 VME QDC\001
5268 4 1 0 0 0 0 14 0.0000 0 180 1125 49523 29306 VME ADC\001
5273 4 1 0 0 0 0 14 0.0000 0 180 1125 37690 29306 VME ADC\001
5291 4 1 0 0 0 0 14 0.0000 0 225 1125 39040 26756 VME QDC\001
5337 4 1 0 0 0 0 14 0.0000 0 225 1125 71823 16056 VME QDC\001
5409 4 1 0 0 0 0 14 0.0000 0 225 1125 29956 31173 VME QDC\001
5443 4 1 0 0 0 0 14 0.0000 0 180 1095 32240 38956 VME TDC\001
5456 4 1 0 0 0 0 14 0.0000 0 180 1125 34723 29306 VME ADC\001
5463 4 1 0 0 0 0 14 0.0000 0 180 1125 28140 29306 VME ADC\001
5578 4 1 0 0 0 0 14 0.0000 0 180 1095 7790 35656 VME TDC\001
[all …]
/dports/emulators/mess/mame-mame0226/src/mame/drivers/
H A Dfccpu20.cpp159 VME(config, "vme", 0); in cpu20()
165 VME(config, "vme", 0); in cpu21s()
171 VME(config, "vme", 0); in cpu21()
177 VME(config, "vme", 0); in cpu21a()
183 VME(config, "vme", 0); in cpu21ya()
189 VME(config, "vme", 0); in cpu21b()
195 VME(config, "vme", 0); in cpu21yb()
/dports/emulators/mame/mame-mame0226/src/mame/drivers/
H A Dfccpu20.cpp159 VME(config, "vme", 0); in cpu20()
165 VME(config, "vme", 0); in cpu21s()
171 VME(config, "vme", 0); in cpu21()
177 VME(config, "vme", 0); in cpu21a()
183 VME(config, "vme", 0); in cpu21ya()
189 VME(config, "vme", 0); in cpu21b()
195 VME(config, "vme", 0); in cpu21yb()
/dports/multimedia/v4l_compat/linux-5.13-rc2/drivers/vme/
H A DKconfig3 # VME configuration.
7 bool "VME bridge support"
10 If you say Y here you get support for the VME bridge Framework.
20 endif # VME
/dports/multimedia/libv4l/linux-5.13-rc2/drivers/vme/
H A DKconfig3 # VME configuration.
7 bool "VME bridge support"
10 If you say Y here you get support for the VME bridge Framework.
20 endif # VME
/dports/multimedia/v4l-utils/linux-5.13-rc2/drivers/vme/
H A DKconfig3 # VME configuration.
7 bool "VME bridge support"
10 If you say Y here you get support for the VME bridge Framework.
20 endif # VME
/dports/multimedia/libv4l/linux-5.13-rc2/drivers/staging/vme/devices/
H A DKconfig2 comment "VME Device Drivers"
5 tristate "VME user space access driver"
9 VME windows in a manner at least semi-compatible with the interface
/dports/multimedia/v4l_compat/linux-5.13-rc2/drivers/staging/vme/devices/
H A DKconfig2 comment "VME Device Drivers"
5 tristate "VME user space access driver"
9 VME windows in a manner at least semi-compatible with the interface
/dports/multimedia/v4l-utils/linux-5.13-rc2/drivers/staging/vme/devices/
H A DKconfig2 comment "VME Device Drivers"
5 tristate "VME user space access driver"
9 VME windows in a manner at least semi-compatible with the interface
/dports/multimedia/v4l_compat/linux-5.13-rc2/drivers/vme/boards/
H A DKconfig2 comment "VME Board Drivers"
9 chip. This driver has to be included if you want to access VME bus
/dports/multimedia/libv4l/linux-5.13-rc2/drivers/vme/boards/
H A DKconfig2 comment "VME Board Drivers"
9 chip. This driver has to be included if you want to access VME bus
/dports/multimedia/v4l-utils/linux-5.13-rc2/drivers/vme/boards/
H A DKconfig2 comment "VME Board Drivers"
9 chip. This driver has to be included if you want to access VME bus
/dports/emulators/tme/tme-0.8/machine/sun3/
H A DSUN3-CARRERA3 ## SUN3-CARRERA - example tmesh commands to create a Sun3 "Carrera" VME
54 ## the sun3 VME buses:
59 ## the Sun "SCSI-2" VME board (shares the Multibus implementation):
66 ## the Sun "SCSI-3" VME board
73 ## the Sun cgthree VME board (handled by the cgtwo emulation):
/dports/multimedia/intel-media-sdk/MediaSDK-intel-mediasdk-22.1.0/doc/
H A DMFE-Overview.md17 * [VME utilization](#vme-utilization)
20 * [VME utilization improvement](#vme-utilization-improvement)
64 VME utilization  
67 …VME utilization. As discussed previously, MB dependencies limit the number of parallel threads (wa…
71 - EU/VME utilization is very low
81 - Result of algorithm and thread dispatching limitations - we can't utilize VME for 100% at high …
83 ###### Figure 3. VME utilization at different SKUs
89 ###### Figure 4. VME utilization result
111 VME utilization improvement
114 VME utilization increased, within the same or near ENC execution time as single frame.
[all …]
/dports/multimedia/libva-intel-driver/intel-vaapi-driver-2.4.1/src/shaders/vme/
H A Dvme.inc137 * r12 write back of VME message
167 * GRF 12~15 -- write back for VME message
185 * GRF 16 -- write back for VME message
264 * VME message payload
/dports/multimedia/v4l-utils/linux-5.13-rc2/arch/m68k/
H A DKconfig.machine49 config VME config
50 bool "VME (Motorola and BVM) support"
54 Say Y here if you want to build a kernel for a 680x0 based VME
62 depends on VME
65 Say Y to include support for early Motorola VME boards. This will
73 depends on VME
76 Say Y to include support for Motorola VME boards. This will build a
85 depends on VME
88 Say Y to include support for VME boards from BVM Ltd. This will
/dports/multimedia/v4l_compat/linux-5.13-rc2/arch/m68k/
H A DKconfig.machine49 config VME config
50 bool "VME (Motorola and BVM) support"
54 Say Y here if you want to build a kernel for a 680x0 based VME
62 depends on VME
65 Say Y to include support for early Motorola VME boards. This will
73 depends on VME
76 Say Y to include support for Motorola VME boards. This will build a
85 depends on VME
88 Say Y to include support for VME boards from BVM Ltd. This will
/dports/multimedia/libv4l/linux-5.13-rc2/arch/m68k/
H A DKconfig.machine49 config VME config
50 bool "VME (Motorola and BVM) support"
54 Say Y here if you want to build a kernel for a 680x0 based VME
62 depends on VME
65 Say Y to include support for early Motorola VME boards. This will
73 depends on VME
76 Say Y to include support for Motorola VME boards. This will build a
85 depends on VME
88 Say Y to include support for VME boards from BVM Ltd. This will
/dports/biology/molden/molden5.8/plush/
H A DVME1 mol="VME" Charge="0"

12345678910>>...21