adds support for ws0010 based character oled displays
Description
Added support for ws0010 based 16x2 character OLED screens
Used the hd77480 lcd driver as reference and ported it to the ws0010 chip used in OLED displays. Most of the commands are the same but the init sequence is quite different. It is integrated in the same manner as the lcd driver in that you define the driver in your rules.mk file and define the pins in config.h. The docs are also located where the hd77480 docs are.
Types of Changes
- [ ] Core
- [ ] Bugfix
- [x ] New feature
- [ ] Enhancement/optimization
- [ ] Keyboard (addition or update)
- [ ] Keymap/layout/userspace (addition or update)
- [ x] Documentation
Issues Fixed or Closed by This PR
Checklist
- [ x] My code follows the code style of this project: C, Python
- [ x] I have read the PR Checklist document and have made the appropriate changes.
- [ x] My change requires a change to the documentation.
- [x ] I have updated the documentation accordingly.
- [ x] I have read the CONTRIBUTING document.
- [ ] I have added tests to cover my changes.
- [ x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).
Is it correct to merge this into the develop branch? I thought I read that in the guidlines but now i'm doubting myself.
Is it correct to merge this into the develop branch? I thought I read that in the guidlines but now i'm doubting myself.
Yes. New features like this go to develop first.
You've pulled in some unrelated changes, please revert this.
Is that better?
i'm not 100% sure what lint wants me to do here. Thought it better to ask than just starting to change things.
Look at the job output, it produces a diff.
some of the lines don't have a + or a - next to them? Do they not need formatting? Are they just for reference or something? Sorry for all the questions, i'm learning.
I recommend you read up a bit on what diffs are. https://stackoverflow.com/questions/2529441/how-to-read-the-output-from-git-diff
thanks, that was a good thread :)
should be fixed now :)
On hold for the moment; from internal discussion there seems to be very limited use cases for this OLED to be used. We're bringing in the concept of "community modules" where certain functionality is kept external to QMK -- the thought is that this would be better suited to that approach instead.
Yeah ok, I get that. I'm using it for a calculator/numpad but I see there aren't a lot of other use cases.