| 10 | |
| 11 | Seskar on 8/25: |
| 12 | |
| 13 | Main issue to date is the use of licensed software (namely Xilinx and Matlab) that is required for FPGA code development. This is especially troublesome for deployments in remotely accessible testbeds not only because it requires that each user have a valid license, but because most academic licenses require that the actual development be done on the machines that belong to the licensee (rather than on the infrastructure machines that the testbed provides). Same issue exists for other FPGA based solutions (like NetFPGA) |
| 14 | |
| 15 | Specification tools like BlueSpec reduce some of these issues (matlab/simulink), but don’t get around basic Xilinx license issue |
| 16 | |
| 17 | Outreach to Xilinx Research at Colorado to explore options |
| 18 | |
| 19 | |
| 20 | Mussman on 8/31: Need to resolve these issues! |