This came up during an onsite HT FPGA class and am not the end user. They have the link to this forum discussion and will reach out to you if it is needed.
Why aren't you using the standard Linux infrastructure for FPGA deployment and control ?
(it's just a matter of few days to add a backend of some new fpga chip, in case you've got some that isn't supported yet).
And why aren't you just adding a new bus driver for your interface, so common things like channels, queues, registers, irqs, etc can be directly supported by existing kernel infrastructure ?
Ah, looks like you're trying to do IRQs in userland. That's funny, especially when calling that "realtime" at the same time. Oh, are that really actual IRQs (that finally trigger the CPUs irq line, which needs to be handled in-kernel), or just some status registers ?
And the really big question remains: how could we ever validate that stuff, w/o any access to the source code and being kept completely in the dark about everything ?
I recommend you post this to the LabVIEW Idea Exchange: https://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas
Does this API help in any way for my Mac to access indicators/controls of FPGA VI that is running on a network cRIO?
My goal is to let my client to read/write access to FPGA VI on cRIO. If not, can you advise what technology I can use to do that? I believe this API requires nifpga.dll so is this Windows only?