Libreboot 26.10 "Ominous Olive" released with UEFI, Chromebook support

Original Article ↗ Hacker News Discussion ↗

Libreboot’s 26.10 “Ominous Olive” release adds UEFI/EDK2 integration and broad Chromebook support, greatly expanding the range of hardware that can run this free boot firmware. At the same time, the project’s aggressively worded ban on AI-assisted contributions has become a lightning rod, with some praising it as a principled extension of software freedom and others criticizing it as ideological, impractical, or technically short-sighted. The exchange highlights a deeper split in open-source culture over whether toolchains using large language models strengthen or undermine code quality, legal safety, and user trust.

Scope of the Release (UEFI & Chromebook Support)

  • Many see UEFI/EDK2 and broad Chromebook support as the technically important part of the release.
  • Importing “MrChromebox” coreboot work multiplies supported Chromebooks; users are excited to revive cheap/old devices.
  • Chromebooks can effectively become generic UEFI laptops running Linux or even Windows.
  • Some note Heads firmware is also adding ChromeOS devices, but doing so is non‑trivial; Libreboot importing many at once is viewed as impressive.

Libreboot vs Coreboot and Blobs

  • Clarified that Libreboot is a distribution of coreboot (prebuilt firmware images and configs), not a fork.
  • Historically blob‑free; now still minimizes blobs and neuters Intel ME, but is no longer fully blobless.
  • A separate project is mentioned as the new “strictly blobless” continuation.

Anti‑AI Policy & AGENTS.md File

  • The new AGENTS.md, aimed at AI tools, is very hostile in tone; some find it funny, others see it as unprofessional or a red flag.
  • Some worry about misuse of AGENTS.md for “prompt injection” or see it as akin to malware for AI agents.
  • Others say the strong stance and “pedantry” are consistent with Libreboot’s mission and culture.

Arguments Against AI Use

  • Claims that AI‑generated code “deskills” developers, produces low‑quality output, and is unsuitable for concise, security‑critical firmware.
  • Concerns about legal/IP contamination (unclear training data, proprietary code leaks) and future liability.
  • Viewed as economically unsustainable and politically dangerous: consolidating control in a few corporations, enabling manipulation of information, and even being called structurally “fascist.”
  • Some insist free software is a political movement, so refusing AI is part of that ethics.

Arguments For / Neutral on AI

  • Others report major productivity gains: rapid reverse engineering, firmware emulation, scripting, bug triage, and kernel‑style code review.
  • Some say early‑2025 critiques are obsolete given perceived quality jumps by late‑2026.
  • A group argues inputs don’t matter—only code quality, correctness, and maintainability should.
  • Some worry strict bans will fragment ecosystems and discourage upstreaming; others respond that forking is always an option.

Broader Free‑Software & Governance Themes

  • Debate over whether “radical” maintainers are necessary to create projects like this or too dogmatic to work with.
  • Many accept: “their repo, their rules,” even if they personally disagree with the AI stance.