AMD pulls a bait-and-switch on Linux users with Vivado licensing changes

Original Article ↗ Hacker News Discussion ↗

AMD’s plan to drop the free Linux tier of its Vivado FPGA development tools, while keeping a free Windows version and paid Linux licenses, has angered many engineers who see it as hostile to hobbyists, academia, and small firms that already must buy AMD hardware. Commenters argue this undermines AMD’s reputation for Linux friendliness and risks driving new projects and future purchasing decisions toward rival FPGA vendors or alternative toolchains. Others speculate the move is driven by support and licensing costs rather than malice, and note rumors that AMD may partially reverse course under backlash.

Change in Vivado Licensing & Immediate Reaction

  • AMD/Xilinx plans (from 2026.1) to drop the free Vivado tier on Linux while keeping:
    • A paid Linux version.
    • A free Windows version.
  • Many Linux users see this as a “foot-gun” and a betrayal of AMD’s reputation for better Linux support.
  • Some argue “bait-and-switch” is the wrong term: Vivado was genuinely free before; this is a policy change, not fake bait.

Business Rationale vs Backlash

  • One view: non‑paying Linux users aren’t real customers; Linux support is costly, and free users generate many support tickets.
  • Counterview: Vivado is required to use AMD FPGAs; revenue comes mainly from hardware (and IP cores), so charging for basic tools discourages hardware adoption.
  • Several note the classic funnel: free/academic tooling leads to future paying enterprise customers; this move cuts off the on‑ramp.

Impact on Linux, Hobbyists, and Ecosystem

  • Hobbyists, students, and small outfits feel directly hit; some consultants say they’ll avoid recommending AMD FPGAs.
  • Suggestions include:
    • Staying on old Vivado versions (some still use 2019/ISE).
    • Running the Windows version via VM or Wine.
  • Concern that fewer free Linux users will mean fewer bug reports, harming quality even for paying customers.

Comparisons to Nvidia/CUDA and GPU World

  • Multiple comparisons to CUDA:
    • CUDA’s success came from wide, free availability; AMD is seen as doing the opposite.
    • Some extrapolate this decision as a signal not to trust AMD for GPU compute either.
  • There is side debate over which vendor supports GPUs longer and more openly on Linux; claims conflict.

Open-Source & Alternative FPGA Toolchains

  • Open-source tools (yosys, nextpnr, etc.) exist and partially support Xilinx 7‑series and some other vendors, but:
    • QoR and timing are said to lag far behind vendor tools.
    • Newer AMD/Xilinx families (US/US+/Versal) lack good open support.
  • Others argue that more reverse engineering of bitstreams/timing is possible but under-resourced.
  • Alternatives mentioned: Lattice (ice40/ECP5) and QuickLogic are seen as more FOSS‑friendly but weaker at the high end.

Trust, Strategy, and Speculation

  • Many say this confirms that large vendors can’t be trusted and strengthens interest in open hardware and indie FPGA efforts.
  • Some speculate about internal bean‑counting, attempts to extract CI/CD “rent”, or even industry collusion; others push back, noting coincidence and lack of evidence.
  • Late in the thread, multiple comments relay rumors (via social media and Reddit) that AMD may walk back the change, but no clear official statement is quoted; status is unclear.