The official replies are addressing questions that nobody has asked. The main issue is why Linux support is being removed from the Basic tier while Windows is still allowed.
To grow the ecosystem, AMD needs more people working on their hardware. Restricting Linux will only alienates students, hobbyists, and devs who want to adopt AMD tech.
I’ve spent several hundred thousand on Xilinx FPGAs yet they nickel and dime me for licenses. It’s not the cost that’s a problem—-it’s the hassle of making a PO for a license to set up new computers, set up CI, hiring new teammates, setting up for interns/students. Xilinx has continued to go downhill since their acquisition by AMD.. it used to feel like it was run by engineers who understood their customers, now it seems to be getting taken over by the MBA crowd who only understands pinching pennies and chiseling their own loyal customers
It's really unfortunate that FPGA development is still stuck in the 90s. The incentives between IP owners and hobbyists are so misaligned that I don't see the possibility of this ever improving.
The market is full of dark patterns, and vendors like AMD/Xilinx can pull shitty moves like what OP highlighted, knowing there is no decent alternative (Altera is another disaster). Lattice had the opportunity to fully embrace opensource toolchain and try to disrupt from the bottom, but they seem stuck in the middle, not wanting to commit one way or another.
I'm grateful to SymbiFlow, and IceStorm and others, even though they obviously lack support for proprietary hardware features.
The difficult part is the place and route algorithm, not the bitstream. The proprietary ones already take quite a long time to solve: I regularly have 12-24h runs. Perhaps an open source one could do better? But it's not quite as straightforward as reverse engineering a proprietary bitstream.
The official replies are addressing questions that nobody has asked. The main issue is why Linux support is being removed from the Basic tier while Windows is still allowed.
To grow the ecosystem, AMD needs more people working on their hardware. Restricting Linux will only alienates students, hobbyists, and devs who want to adopt AMD tech.
- From long term AMD user
I’ve spent several hundred thousand on Xilinx FPGAs yet they nickel and dime me for licenses. It’s not the cost that’s a problem—-it’s the hassle of making a PO for a license to set up new computers, set up CI, hiring new teammates, setting up for interns/students. Xilinx has continued to go downhill since their acquisition by AMD.. it used to feel like it was run by engineers who understood their customers, now it seems to be getting taken over by the MBA crowd who only understands pinching pennies and chiseling their own loyal customers
Link to AMDs description of the new pricing being criticized: https://www.amd.com/en/products/software/adaptive-socs-and-f...
I love the way they buried the “we are no longer supporting an entire operating system” in a small missing tick, half way down the page…
Good news for FOSS FPGA toolchains, I suppose. Eg https://f4pga.org/ for some kind of umbrella project.
It's really unfortunate that FPGA development is still stuck in the 90s. The incentives between IP owners and hobbyists are so misaligned that I don't see the possibility of this ever improving.
The market is full of dark patterns, and vendors like AMD/Xilinx can pull shitty moves like what OP highlighted, knowing there is no decent alternative (Altera is another disaster). Lattice had the opportunity to fully embrace opensource toolchain and try to disrupt from the bottom, but they seem stuck in the middle, not wanting to commit one way or another.
I'm grateful to SymbiFlow, and IceStorm and others, even though they obviously lack support for proprietary hardware features.
I wonder how good LLM agents are at reverse engineering FPGA bitstreams...
I want a robust open-source ecosystem where anyone can take my hardware projects and modify them without needing to deal with licensing friction.
The difficult part is the place and route algorithm, not the bitstream. The proprietary ones already take quite a long time to solve: I regularly have 12-24h runs. Perhaps an open source one could do better? But it's not quite as straightforward as reverse engineering a proprietary bitstream.