Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add Pinky(https://github.com/tamanishi/Pinky3) keyboard #4748

Merged
merged 6 commits into from
Jan 5, 2019
Merged

add Pinky(https://github.com/tamanishi/Pinky3) keyboard #4748

merged 6 commits into from
Jan 5, 2019

Conversation

tamanishi
Copy link
Contributor

@tamanishi tamanishi commented Dec 30, 2018

This PR adds my new "Pinky" keyboard firmware.

Description

Add my new "Pinky" keyboard firmware.

Types of changes

  • Core
  • Bugfix
  • New Feature
  • Enhancement/Optimization
  • Keyboard (addition or update)
  • Keymap/Layout/Userspace (addition or update)
  • Documentation

Issues Fixed or Closed by this PR

  • none

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document. (https://docs.qmk.fm/#/contributing)
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

@drashna
Copy link
Member

drashna commented Dec 30, 2018

If you have two different revisions of the PCB (3 and 4 pinky), you should really use these as the "revision", instead of using a configuration in the keymap (and rules.mk).

Put most everything in the main folder, but change the pin defines in the subfolders, and then have a seperate keymap folder in each of these revisions.

It would be a lot cleaner here.

@tamanishi
Copy link
Contributor Author

Thank you for reviewing.
I separated revisions 3 and 4.

keyboards/pinky/3/keymaps/default/keymap.c Outdated Show resolved Hide resolved
keyboards/pinky/3/keymaps/default/keymap.c Outdated Show resolved Hide resolved
keyboards/pinky/3/keymaps/default/keymap.c Outdated Show resolved Hide resolved
keyboards/pinky/3/3.c Show resolved Hide resolved
keyboards/pinky/4/4.c Show resolved Hide resolved
keyboards/pinky/3/config.h Show resolved Hide resolved
keyboards/pinky/4/config.h Show resolved Hide resolved
keyboards/pinky/config.h Outdated Show resolved Hide resolved
@tamanishi
Copy link
Contributor Author

Happy New Year!
Thank you for reviewing.
I hope that I improved the items was pointed out above.

Copy link
Member

@drashna drashna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It appears that theys keyboard is using the normal split code (well, mtei's modified code), and doesn't use an SSD1306 OLED screen, at all.

If this is the case, then you should actually use the Split Common code instead.

In this case, you would need to remove the i2c, serial, matrix and split_util files from the keyboard folders, and you'd want to set SPLIT_KEYBOARD to yes.

The rest of the settings would remain the same, as mtei has merged most of this code into the core split common code.

The reason I am asking to do this, is that it would keep your board up to date with any of the newer changes, so that they don't have to be maintained separately.

keyboards/pinky/pro_micro.h Outdated Show resolved Hide resolved
keyboards/pinky/rules.mk Outdated Show resolved Hide resolved
keyboards/pinky/rules.mk Outdated Show resolved Hide resolved
keyboards/pinky/rules.mk Outdated Show resolved Hide resolved
@tamanishi
Copy link
Contributor Author

Thank you for reviewing.
I removed the i2c, serial, matrix and split_util files.
And I regenerated some files from the template files, because the right side slave device didn't work.
Now it works.

@@ -0,0 +1,46 @@
#pragma once

#include "../pinky.h"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't actually need the ".." here.

When compiling, both the subfolder and main folder (eg, pinky, and 3 in this case) are added to the "common path". So, you can call "pinky.h" directly, without having to use it's relative path.

It's fin to do this, but "for the future"... it's something to keep in mind.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understood. I'll keep that in mind.

@drashna
Copy link
Member

drashna commented Jan 5, 2019

Awesome, thanks!

@drashna drashna merged commit ac7a9e3 into qmk:master Jan 5, 2019
Shinichi-Ohki added a commit to Shinichi-Ohki/qmk_firmware that referenced this pull request Jan 10, 2019
* 'master' of https://github.com/qmk/qmk_firmware: (63 commits)
  Keymap: ave-63's iris layout (qmk#4812)
  Update bakingpy 4x12 keymap and add test mode for debugging/development (qmk#4810)
  Fix Mac mute keycode (qmk#4809)
  Add KBD75 keymap (qmk#4808)
  Fix pinout of split hand and LED, remove flip half option
  Tidy up Mod-Tap shortcuts (qmk#4806)
  Add missing parentheses to some important macros (qmk#4775)
  Keyboard: Downbubble refactor and Configurator fix (qmk#4798)
  Alternate keymap for Alpha keyboard, enjoy! (qmk#4797)
  Keymap: Added Model F-inspired layout for YMD[K]96 (qmk#4777)
  Improve consistency in UNICODEMAP code and docs, update docs/understanding_qmk (qmk#4774)
  Update to arm_atsam wait and timer routines
  Add Downbubble to Handwired repository (qmk#4794)
  Final HS60v2 changes. (qmk#4790)
  Keyboard: Fractal layout macro and readme cleanup (qmk#4789)
  Keymap: added my espectro keymap (qmk#4791)
  Keyboard: Numbrero: Configurator fix and code tidy (qmk#4787)
  Keyboard: Tradestation code tidy and readme refactor (qmk#4784)
  Keyboard: update readme with ps2avr flashing instructions (qmk#4776)
  add Pinky keyboard (qmk#4748)
  ...
rseymour pushed a commit to rseymour/qmk_firmware that referenced this pull request Mar 13, 2019
djthread pushed a commit to djthread/qmk_firmware that referenced this pull request Mar 17, 2019
dlhextall pushed a commit to dlhextall/qmk_firmware that referenced this pull request May 24, 2019
@Canorus Canorus mentioned this pull request Jun 3, 2024
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants