Oct 17, 2026, 1:42 AMretooted elly
#netbsd on a Chromebook, because WCGW?
Standard ACPI stuff like CPU temperature reading, battery reporting, ATKBD or screen brightness does work.
However, nothing related to EC work (TigerLake and newer will not boot from USB-C due to Mux introduced in that generation, EC will also enter failsafe mode after few minutes, start ramping the fan up and hard power-off due to no response from nonexistent driver).
Graphical corruption in X11 (which also happens on Linux, this thing has a 4K display and works correctly only in Wayland).
Biggest surprise is that I2C seems broken, so touchpad/touchscreen/stylus probably wouldn't work (although I expect to beissing drivers for those devices as well).
Sound and WiFi of course doesn't work (Chromebooks use SOF, so it's not a standard HDA configuration and adding support for audio DSP would be... quite a lot of work) and WiFi is an Intel AX201 (cnvi), so obviously no luck there.
Probably biggest suprise to me is that NetBSD (seemingly) has zero complains about coreboot's ACPI, the only (mis)reporting of ACPI error is that it had no idea how to parse CrosEC stuff.
I'm positively surprised. Being the one to potentially write missing platform drivers sounds fun, I can implement some stuff I had in mind but maintainers of `platforms/chrome` in Linux absolutely hated :blobcat3c:
I think I'm gonna add NetBSD to my standard testing suite while working on coreboot, not just Linux and Windows.
Standard ACPI stuff like CPU temperature reading, battery reporting, ATKBD or screen brightness does work.
However, nothing related to EC work (TigerLake and newer will not boot from USB-C due to Mux introduced in that generation, EC will also enter failsafe mode after few minutes, start ramping the fan up and hard power-off due to no response from nonexistent driver).
Graphical corruption in X11 (which also happens on Linux, this thing has a 4K display and works correctly only in Wayland).
Biggest surprise is that I2C seems broken, so touchpad/touchscreen/stylus probably wouldn't work (although I expect to beissing drivers for those devices as well).
Sound and WiFi of course doesn't work (Chromebooks use SOF, so it's not a standard HDA configuration and adding support for audio DSP would be... quite a lot of work) and WiFi is an Intel AX201 (cnvi), so obviously no luck there.
Probably biggest suprise to me is that NetBSD (seemingly) has zero complains about coreboot's ACPI, the only (mis)reporting of ACPI error is that it had no idea how to parse CrosEC stuff.
I'm positively surprised. Being the one to potentially write missing platform drivers sounds fun, I can implement some stuff I had in mind but maintainers of `platforms/chrome` in Linux absolutely hated :blobcat3c:
I think I'm gonna add NetBSD to my standard testing suite while working on coreboot, not just Linux and Windows.