From 3b2e1396c08e1951e11d1e66e5606e80bd4090e1 Mon Sep 17 00:00:00 2001 From: Adam Honse Date: Tue, 21 Dec 2021 01:23:02 -0600 Subject: [PATCH] Update warning in README --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index f931f63d..e72672d5 100644 --- a/README.md +++ b/README.md @@ -32,9 +32,8 @@ This project interacts directly with hardware using reverse engineered protocols There have been two instances of hardware damage in OpenRGB's development and we've taken precautions to prevent it from happening again. - * The MSI Mystic Light code reportedly bricked the RGB on certain MSI boards when sending certain modes. This code has been disabled and MSI Mystic Light motherboards will not work with OpenRGB at this time. + * The Mystic Light motherboard code bricked the RGB controller of some MSI motherboards. The code was disabled and reworked. We have been re-adding these motherboards to the support list as we verify that the new code works with them. Affected boards can be unbricked with a Nuvoton Nu-Link adapter. * There were reports of bricked Gigabyte Aorus Z390 motherboards caused by dumping SMBus address 0x68 in an attempt to reverse engineer the RGB. Due to this, the SMBus Tools page on OpenRGB is hidden by default now as it has no real use to non-developers. - * To enable the MSI Mystic Light code, you must uncomment the detection macro in the Mystic Light controller detection code and recompile. ![OpenRGB_Device_View](https://gitlab.com/CalcProgrammer1/OpenRGB/-/wikis/uploads/e1d8d4603ecdd04f1acbcf6b2314fc66/OpenRGB_0.31_Device_View.PNG)