Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It does beg the question whether this is simply a chicken-and-egg problem.

When it is almost impossible to develop for, you only get big contracts because nobody else has the resources to design products for it. On the other hand, with good and free design tools the toy projects done by hobbyists and schools can serve as the catalyst for using it in medium-scale projects.

There are plenty of applications imaginable for something like Intel's SmartNIC platform - but you're not going to see any of them unless tinkerers can get their hands on them.



Indeed.

Xilinx, for example, used to be very friendly about making really cheap or even free FPGAs available to academic users. This is because those users lead either directly to design wins (some academic designs go big, NSF style) or they become corporate users who are familiar with Xilinx gear.

But the software was crap, and they would have gotten more wins if the software wasn’t so awful.


Xilinx/AMD doesn't make overt donations any more AFAIK, but they still subsidize hardware as a loss leader and for academics. For example, academic groups can buy the RFSoC 4x2 board for $2149 USD, which is a small fraction of the volume price of the chip that's on it.

"EDA software is crap" is so close to an axiom around here that I think Vivado doesn't get the credit it deserves. The synthesis flow has been rapidly modernizing and supports a chunk of VHDL-2019. The bundled simulator still lags on support and features, for reasons that are pretty easy to understand.


> Xilinx/AMD doesn't make overt donations any more AFAIK

That’s too bad. I once got a small pile (8?) of max-spec Virtex-5 chips, for free, FedExed from Xilinx. Xilinx apparently valued them so little that they didn’t even bother putting the full address on the envelope. Tracking it down was fun.

The only remotely supportable way to synthesize images for them was to run a primitive CentOS 5 container on a big server — the Windows version of the tools were still 32-bit, and 4G of address space was too little for the synthesis workflow. Even with the magic 64-bit RHEL/CentOS-only build, it would take 45 minutes or so for the tools to notice any errors during synthesis.

Fun times.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: