by Guest »
Hi Eli,
A high-level question. I currently writing FSM based on the content of `xilly_mem_32` block and a thread on host that can start a hardware thread on FPGA.
It is very similar to the concept of 'on the fly computing' according to: `http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=6913232`. In that paper and following papers people go to the direction of ReconOS and some people want to port ReconOS to x86-based server systems.
Is there any need of adapt ReconOS to the x86-host? Why I feel that Xillybus with Linux/Windows could implement the same functionality?
What is truly needed is just a host pooling thread in Linux/Windows that write seekable content to the RAM, and multiple customised FSMs based on the content of the RAM. Isn't the ReconOS the same thing based on this description?
What do you think?
Best,
Chongxi
Hi Eli,
A high-level question. I currently writing FSM based on the content of `xilly_mem_32` block and a thread on host that can start a hardware thread on FPGA.
It is very similar to the concept of 'on the fly computing' according to: `http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=6913232`. In that paper and following papers people go to the direction of ReconOS and some people want to port ReconOS to x86-based server systems.
Is there any need of adapt ReconOS to the x86-host? Why I feel that Xillybus with Linux/Windows could implement the same functionality?
What is truly needed is just a host pooling thread in Linux/Windows that write seekable content to the RAM, and multiple customised FSMs based on the content of the RAM. Isn't the ReconOS the same thing based on this description?
What do you think?
Best,
Chongxi