diff options
| author | Drashna Jaelre <drashna@live.com> | 2020-11-02 16:17:05 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-11-03 00:17:05 +0000 |
| commit | 38162af5a70ced55f74019b75ed1e2f1e03ff62e (patch) | |
| tree | e91a123d13233a7468dbfd61601988b16d4b8dac /keyboards/ploopyco/mouse | |
| parent | e680af98d2347222ba41b5affc941e6682e0ce34 (diff) | |
[Keyboard] Fixes for PloopyCo mouse and readmes (#10841)
Diffstat (limited to 'keyboards/ploopyco/mouse')
| -rw-r--r-- | keyboards/ploopyco/mouse/mouse.c | 2 | ||||
| -rw-r--r-- | keyboards/ploopyco/mouse/readme.md | 27 | ||||
| -rw-r--r-- | keyboards/ploopyco/mouse/rules.mk | 2 |
3 files changed, 3 insertions, 28 deletions
diff --git a/keyboards/ploopyco/mouse/mouse.c b/keyboards/ploopyco/mouse/mouse.c index fad4807c78..7e44feaf74 100644 --- a/keyboards/ploopyco/mouse/mouse.c +++ b/keyboards/ploopyco/mouse/mouse.c @@ -140,7 +140,7 @@ __attribute__((weak)) void process_mouse(report_mouse_t* mouse_report) { if (debug_mouse) dprintf("Cons] X: %d, Y: %d\n", data.dx, data.dy); // dprintf("Elapsed:%u, X: %f Y: %\n", i, pgm_read_byte(firmware_data+i)); - process_mouse_user(mouse_report, data.dx, data.dy); + process_mouse_user(mouse_report, data.dx, -data.dy); } } diff --git a/keyboards/ploopyco/mouse/readme.md b/keyboards/ploopyco/mouse/readme.md index a9b4b581a3..fd0f932c62 100644 --- a/keyboards/ploopyco/mouse/readme.md +++ b/keyboards/ploopyco/mouse/readme.md @@ -2,9 +2,8 @@  -It's a DIY, QMK Powered Trackball!!!! +It's a DIY, QMK Powered Mouse!!!! -Everything works. However the scroll wheel has some issues and acts very odd. * Keyboard Maintainer: [PloopyCo](https://github.com/ploopyco), [Drashna Jael're](https://github.com/drashna/), [Germ](https://github.com/germ/) * Hardware Supported: ATMega32u4 8MHz(3.3v) @@ -51,27 +50,3 @@ To configure/set your own array, there are two defines to use, `PLOOPY_DPI_OPTIO The `PLOOPY_DPI_OPTIONS` array sets the values that you want to be able to cycle through, and the order they are in. The "default" define lets the firmware know which of these options is the default and should be loaded by default. The `DPI_CONFIG` macro will cycle through the values in the array, each time you hit it. And it stores this value in persistent memory, so it will load it the next time the device powers up. - - -# Programming QMK-DFU onto the PloopyCo Mouse - -If you would rather have DFU on this board, you can use the QMK-DFU bootloader on the device. To do so, you want to run: - - make ploopyco/trackball:default:production - -Once you have that, you'll need to [ISP Flash](https://docs.qmk.fm/#/isp_flashing_guide) the chip with the new bootloader hex file created (or the production hex), and set the fuses: - - -| Fuse | Setting | -|----------|------------------| -| Low | `0xDF` | -| High | `0xD8` or `0x98` | -| Extended | `0xCB` | - -Original (Caterina) settings: - -| Fuse | Setting | -|----------|------------------| -| Low | `0xFF` | -| High | `0xD8` | -| Extended | `0xFE` | diff --git a/keyboards/ploopyco/mouse/rules.mk b/keyboards/ploopyco/mouse/rules.mk index db72641d0c..863f335c85 100644 --- a/keyboards/ploopyco/mouse/rules.mk +++ b/keyboards/ploopyco/mouse/rules.mk @@ -5,7 +5,7 @@ MCU = atmega32u4 F_CPU = 8000000 # Bootloader selection -BOOTLOADER = qmk-dfu +BOOTLOADER = atmel-dfu # Build Options # change yes to no to disable |