| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
miod explained it was initially a long as it was thought drivers may
need to allocate storage but in practice they don't need more than
32 bits for an attribute.
suggested and reviewed by miod@
|
| |
|
|
|
| |
from the userland. Also allow changing the brightness levels so that
it can even be turned off to save power and to prevent burn in.
|
| |
|
|
|
|
| |
only allocated and used for the SPI backend.
From Tobias Nygren
|
| |
|
|
| |
a NanoHat OLED.
|
| | |
|
| |
|
|
|
| |
since some OLED display controller settings can change depending on the
actual hardware integration.
|
| |
|
|
|
|
|
| |
the characters that changed, and only when they change. This
replaces writing out the whole framebuffer every 100ms with a
partial update mechanism. Now the system stays responsive and
does not slow down anymore due to the periodic update.
|
| |
|
|
|
| |
and SPI bus is simply how to let the chip know it's a command or data
transfer. Otherwise we push the very same bits.
|
| |
|
|
|
|
|
| |
cannot read the framebuffer memory, we have to push the framebuffer to
the display. ssdfb(4) will now be able to update only a certain region
region of the framebuffer as soon as there is infrastructure to trigger
it.
|
| |
|
|
|
|
| |
the 8x16 font showed horizontally flipped characters, but as it turns
out the issue is that with 8-bit wide fonts we use optimized rasops
code that apparently writes out the character with reversed bitorder.
|
|
|
128x64 OLED display. With the typical 8x16 font we get 4 rows with
16 characters each on it. The controller can be driven using I2C,
3-wire and 4-wire SPI. This commit includes support for the 4-wire
protocol.
ok deraadt@
|
jsg
patrick