OpenBSD 8.0 release will have inteldrm/radeondrm/amdgpu drivers from Linux 6.18

📝 Discussion Summary (Click to expand)

Three Prevalent Themes

Speculation about LLMs aiding driver/hardware support – Commenters wonder whether LLMs are secretly used to reverse‑engineer proprietary hardware and improve suspend/hibernate on Linux/*BSD.

“will LLMs actually help Linux and smaller OSes by accelerating reverse engineering hardware that doesn’t have open/good enough specs? Will we reach a point where hibernate works reliably on Linux?” — oblio
OpenBSD’s versioning and release philosophy – Discussion clarifies that OpenBSD uses a fixed‑six‑month schedule where version numbers increase linearly, and every release may contain breaking changes.

“Note that OpenBSD is on 7.9 now and all releases are possible breaking changes. They release every six month and increment by 0.1. And after 0.9 they rollover to the next whole number.” — alberth
Licensing compatibility of GPL‑covered code with BSD kernels – Contributors explain how MIT‑licensed DRM drivers can be used in OpenBSD, while the project maintains a strict “no GPL” policy in its kernel.

“OpenBSD has a strict 'no GPL' policy. It does not incorporate GPL code in the kernel, and it has slowly weeded out GPL code from userland. This is one reason why it builds with Clang instead of GCC.” — nanolith

🚀 Project Ideas

Generating project ideas…

Uses LLMs to ingest hardware datasheets, register dumps, and existing Linux driver source to generate concise hardware specifications and driver stubs for BSDs.
Core value proposition: dramatically reduces manual reverse‑engineering effort, enabling reliable hibernation and GPU support on Linux/*BSD.

Key	Value
Target Audience	Kernel developers, porting engineers working on Linux/*BSD driver support for undocumented hardware
Core Feature	LLM‑driven spec extraction and driver skeleton generation from binary blobs or datasheets
Tech Stack	Python, HuggingFace Transformers (CodeLlama), SPDX parser, Clang AST, GitHub Actions
Difficulty	Medium
Monetization	Hobby

Commenters wondered if LLMs could help reverse engineer hardware for better hibernation support (see oblio: “Will LLMs actually help Linux and smaller OSes by accelerating reverse engineering hardware…?”).
Automating spec extraction would lower the toil mentioned by andrewchambers (“People who have been doing something for years are exactly the people who benefit the most from having pointless toil removed”).

Automates tracking of Linux DRM/GPU driver updates, translates MIT‑licensed code to BSD‑compatible licenses, runs compliance checks, and generates ready‑to‑apply patches for OpenBSD/FreeBSD.
Core value proposition: eliminates manual re‑syncing and licensing guesswork, keeping BSD GPU stacks current with minimal effort.

Key	Value
Target Audience	BSD maintainers, ports teams, and contributors who regularly backport Linux drivers
Core Feature	Automated diff generation, license conversion, and CI‑verified patch creation for Linux→BSD driver ports
Tech Stack	Go, libgit2, license‑scanner (scancode), Docker, Buildkite/GitHub Actions
Difficulty	High
Monetization	Hobby

asveikau noted the continuous effort to re‑sync Linux video drivers to OpenBSD (“The *BSDs have been porting Linux video drivers for years… They need to re‑sync with upstream periodically”).
andrewchambers highlighted that experienced developers would benefit from removing pointless toil, exactly what this suite provides.

A daemon that runs early in boot, detects missing firmware blobs via kernel messages, queries a community‑maintained metadata service, and securely downloads/installs the required blobs with user consent.
Core value proposition: removes the need for manual fw_update and prevents hardware (e.g., Wi‑Fi, GPU) from being non‑functional due to missing firmware.

Key	Value
Target Audience	End‑users of Linux/*BSD laptops and embedded devices who encounter “firmware not found” errors
Core Feature	Automatic detection, authenticated download, and installation of missing firmware blobs
Tech Stack	Rust (for safety), libudev, JSON‑REST metadata server, TPM‑based verification, systemd service
Difficulty	Medium
Monetization	Hobby

rootnod3 mentioned that firmware blobs are downloaded after installation via fw_update; users often miss this step, leading to non‑working hardware (e.g., hibernate).
Providing a seamless, automatic solution would be welcomed by users frustrated with manual firmware handling and would reduce support threads on HN.