diff options
| author | Joel Challis <git@zvecr.com> | 2022-07-31 20:33:12 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-31 12:33:12 -0700 |
| commit | c10c2575b8f71b5fccad6a50bf79bacc7b3caeaf (patch) | |
| tree | 0e70219a95a05abdb78557d623be4f8e728f096b | |
| parent | 2f19579d3f2c8b4041f0128976c00136c5a6a32d (diff) | |
| download | qmk_firmware-c10c2575b8f71b5fccad6a50bf79bacc7b3caeaf.tar.gz qmk_firmware-c10c2575b8f71b5fccad6a50bf79bacc7b3caeaf.zip | |
Remove OLED driver Split Common warning (#17862)
| -rw-r--r-- | docs/feature_oled_driver.md | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/docs/feature_oled_driver.md b/docs/feature_oled_driver.md index 0d04f007f8..f73909f486 100644 --- a/docs/feature_oled_driver.md +++ b/docs/feature_oled_driver.md @@ -14,8 +14,6 @@ Tested combinations: Hardware configurations using Arm-based microcontrollers or different sizes of OLED modules may be compatible, but are untested. -!> Warning: This OLED driver currently uses the new i2c_master driver from Split Common code. If your split keyboard uses I2C to communicate between sides, this driver could cause an address conflict (serial is fine). Please contact your keyboard vendor and ask them to migrate to the latest Split Common code to fix this. In addition, the display timeout system to reduce OLED burn-in also uses Split Common to detect keypresses, so you will need to implement custom timeout logic for non-Split Common keyboards. - ## Usage To enable the OLED feature, there are two steps. First, when compiling your keyboard, you'll need to add the following to your `rules.mk`: |