summaryrefslogtreecommitdiff
path: root/docs/feature_split_keyboard.md
diff options
context:
space:
mode:
authorcoliss86 <coliss86@users.noreply.github.com>2022-06-19 00:32:22 +0200
committerGitHub <noreply@github.com>2022-06-19 08:32:22 +1000
commitfd01feae4b4dc01ff797754748fa822b2a07fbcb (patch)
tree9f1d843630c0640c4835460b2c798328215d6972 /docs/feature_split_keyboard.md
parentb5104c3a93942aa531540d5f46bd58cd5b3cdb46 (diff)
Add a note about using differents MCU family (#17416)
Diffstat (limited to 'docs/feature_split_keyboard.md')
-rw-r--r--docs/feature_split_keyboard.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/feature_split_keyboard.md b/docs/feature_split_keyboard.md
index 6ef70bf788..eefafdbf75 100644
--- a/docs/feature_split_keyboard.md
+++ b/docs/feature_split_keyboard.md
@@ -10,6 +10,8 @@ For this, we will mostly be talking about the generic implementation used by the
!> ARM split supports most QMK subsystems when using the 'serial' and 'serial_usart' drivers. I2C slave is currently unsupported.
+!> Both sides must use the same MCU family, for eg two Pro Micro-compatible controllers or two Blackpills. Currently, mixing AVR and ARM is not possible as ARM vs AVR uses different method for serial communication, and are not compatible. Moreover Blackpill's uses 3.3v logic, and atmega32u4 uses 5v logic.
+
## Compatibility Overview
| Transport | AVR | ARM |