You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Q:** What are the differences between on-premise FPGAs and NP VMs?
212
+
**Q:** What are the differences between on-premises FPGAs and NP VMs?
213
213
214
214
**A:**
215
215
<br>
216
216
<b>- Regarding XOCL/XCLMGMT: </b>
217
217
<br>
218
218
On Azure NP VMs, only the role endpoint (Device ID 5005), which uses the XOCL driver, is present.
219
219
220
-
In on-premise FPGAs, both the management endpoint (Device ID 5004) and role endpoint (Device ID 5005), which use the XCLMGMT and XOCL drivers respectively, are present.
220
+
In on-premises FPGAs, both the management endpoint (Device ID 5004) and role endpoint (Device ID 5005), which use the XCLMGMT and XOCL drivers respectively, are present.
[M2M data transfer](https://xilinx.github.io/XRT/master/html/m2m.html).
237
237
<br>
238
238
This feature isn't supported in Azure NP VMs.
@@ -256,6 +256,6 @@ This feature isn't supported in Azure NP VMs.
256
256
257
257
**Q:** Do Azure NP VMs support FPGA bitstreams with Networking GT Kernel connections?
258
258
259
-
**A:** No. The FPGA Attestation service performs a series of validations on a design checkpoint file and will generate an error if the user's application contains connections to the FPGA card's QSFP networking ports.
259
+
**A:** No. The FPGA Attestation service performs a series of validations on a design checkpoint file and generates an error if the user's application contains connections to the FPGA card's QSFP networking ports.
0 commit comments