Projectidea: UEFI Validation OS - LuvOS

[MaCXyLo]

Heyyo,
i stumbled about the following stuff:
https://01.org/linux-uefi-validation/

This "Linux-readiness" distribution provides a new level of support to developers identifying firmware implementation issues. Bringing together multiple separate upstream test suites into a cohesive and easy-to-use product with a unified reporting framework, LUV validates UEFI firmware at critical levels of the software stack.

LUV also provides tests in areas not previously available, such as the interaction between the bootloader, Linux kernel and firmware. Integrated into one Linux distribution, firmware can now be tested under conditions that are closer to real scenarios of operation. The result: fewer firmware issues disrupting the operating system.

LUV is a collection of test suites, not a certification tool for Linux or UEFI compliance, nor a replacement for existing individual test suite projects.

the firmware testsuite (also called fwts) from canonical (the producer of ubuntu) and CHIPSEC is also included.

Firmware Test Suite (FWTS) is a test suite that performs sanity checks on Intel/AMD PC firmware. It is intended to identify BIOS and ACPI errors and if appropriate it will try to explain the errors and give advice to help workaround or fix firmware bugs. It is primarily intended to be a Linux-centric firmware troubleshooting tool.

https://wiki.ubuntu.com/FirmwareTestSuite

CHIPSEC is a framework for analyzing the security of PC platforms including hardware, system firmware (BIOS/UEFI), and platform components. It includes a security test suite, tools for accessing various low level interfaces, and forensic capabilities.

https://github.com/chipsec/chipsec

The problem with firmware on notebooks and other devices is:
it’s often poorley implemented and not well tested. Firmware bugs on several devices are common things.

so my idea is:
pressurize the producer of hardware to fix they’re shit.
why:
if you buy a notebook, you want regulary know if the manufacturer done the implementation right. otherwise you are buying the cat in sack.

how:
a public report database with firmware reports/bugs.
is anybody @ this board interested to get this thing done?

Kind Regards,