mirrors/keychron_qmk_firmware
mirrors/keychron_qmk_firmware
0
0
Fork 0
mirror of https://github.com/Keychron/qmk_firmware.git synced 2024-12-27 11:38:58 +06:00
Code Issues Packages Projects Releases Wiki Activity
9632360caa
keychron_qmk_firmware/users/drashna/oled
History
Jeff Epler 9632360caa
Use a macro to compute the size of arrays at compile time (#18044) 
* Add ARRAY_SIZE and CEILING utility macros

* Apply a coccinelle patch to use ARRAY_SIZE

* fix up some straggling items

* Fix 'make test:secure'

* Enhance ARRAY_SIZE macro to reject acting on pointers

The previous definition would not produce a diagnostic for
```
int *p;
size_t num_elem = ARRAY_SIZE(p)
```
but the new one will.

* explicitly get definition of ARRAY_SIZE

* Convert to ARRAY_SIZE when const is involved

The following spatch finds additional instances where the array is
const and the division is by the size of the type, not the size of
the first element:
```
@ rule5a using "empty.iso" @
type T;
const T[] E;
@@

- (sizeof(E)/sizeof(T))
+ ARRAY_SIZE(E)

@ rule6a using "empty.iso" @
type T;
const T[] E;
@@

- sizeof(E)/sizeof(T)
+ ARRAY_SIZE(E)
```

* New instances of ARRAY_SIZE added since initial spatch run

* Use `ARRAY_SIZE` in docs (found by grep)

* Manually use ARRAY_SIZE

hs_set is expected to be the same size as uint16_t, though it's made
of two 8-bit integers

* Just like char, sizeof(uint8_t) is guaranteed to be 1

This is at least true on any plausible system where qmk is actually used.

Per my understanding it's universally true, assuming that uint8_t exists:
https://stackoverflow.com/questions/48655310/can-i-assume-that-sizeofuint8-t-1

* Run qmk-format on core C files touched in this branch

Co-authored-by: Stefan Kerkmann <karlk90@pm.me>
2022-08-30 10:20:04 +02:00
..
drashna_font.h [Keymap] Reorganization, cleanup and readmes for drashna code (#15617) 2021-12-29 20:17:34 -08:00
oled_config.h [Keymap] Drashna keymap updates for 0.18.0 (#18184) 2022-08-28 12:55:19 -07:00
oled_stuff.c Use a macro to compute the size of arrays at compile time (#18044) 2022-08-30 10:20:04 +02:00
oled_stuff.h [Keymap] Drashna keymap updates for 0.18.0 (#18184) 2022-08-28 12:55:19 -07:00
readme.md [Keymap] Reorganization, cleanup and readmes for drashna code (#15617) 2021-12-29 20:17:34 -08:00
sh110x.c [Keymap] Updates to drashna Keymaps and Userspace (#17543) 2022-07-02 19:55:46 -07:00

readme.md

OLED Display

To disable the pre genrated oled display, add CUSTOM_OLED_DRIVER = no to your rules.mk.

OLED Font

My font file has multiple fonts and multiple logs integrated into the one file. And it uses the full 255 possible characters.

In addition to the default font and logos:

#    define OLED_FONT_5X5
#    define OLED_FONT_AZTECH
#    define OLED_FONT_BMPLAIN
#    define OLED_FONT_CRACKERS
#    define OLED_FONT_EIN
#    define OLED_FONT_HISKYF21
#    define OLED_FONT_SQUASH
#    define OLED_FONT_SUPER_DIGG
#    define OLED_FONT_ZXPIX

#    define OLED_LOGO_CORNE
#    define OLED_LOGO_GMK_BAD
#    define OLED_LOGO_GOTHAM
#    define OLED_LOGO_HUE_MANITEE
#    define OLED_LOGO_LOOSE
#    define OLED_LOGO_SETS3N
#    define OLED_LOGO_SKEEB

Additionally, the font file allows for external oled font files, instead. This allows for additional files that cannot be hosted in the QMK Repo.

Display

A picture is worth a thousand words. So here are two:

Right

Left