summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorQMK Bot <hello@qmk.fm>2021-01-11 05:49:10 +0000
committerQMK Bot <hello@qmk.fm>2021-01-11 05:49:10 +0000
commit14d2e40babc0d52ce3b69809da2647b6dfe1df14 (patch)
treea6dc526a60d036c4fa6664e557265fb50ce09f74
parent1e0866325c07c32a029cc5d762c36f73e6e320f1 (diff)
parentefbaf68d5ace3a8f574cc1e3ae375a9f1d7fd0ba (diff)
Merge remote-tracking branch 'origin/master' into develop
-rw-r--r--docs/hardware_avr.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/hardware_avr.md b/docs/hardware_avr.md
index 2c0f2e9a1a..42f4a799d2 100644
--- a/docs/hardware_avr.md
+++ b/docs/hardware_avr.md
@@ -77,7 +77,7 @@ Do change the `MANUFACTURER` and `PRODUCT` lines to accurately reflect your keyb
#define PRODUCT my_awesome_keyboard
```
-?> Windows and macOS will display the `MANUFACTURER` and `PRODUCT` in the list of USB devices. `lsusb` on Linux instead takes these from the list maintained by the [USB ID Repository](http://www.linux-usb.org/usb-ids.html) by default. `lsusb -v` will show the values reported by the device, and they are also present in kernel logs after plugging it in.
+?> Windows and macOS will display the `MANUFACTURER` and `PRODUCT` in the list of USB devices. `lsusb` on Linux instead prefers the values in the list maintained by the [USB ID Repository](http://www.linux-usb.org/usb-ids.html). By default, it will only use `MANUFACTURER` and `PRODUCT` if the list does not contain that `VENDOR_ID` / `PRODUCT_ID`. `sudo lsusb -v` will show the values reported by the device, and they are also present in kernel logs after plugging it in.
### Keyboard Matrix Configuration