swaitsandClaude Opus 4.6
3102fc747a
Implement full SSD1306 OLED display support: - Splash screen on boot (1.5s) with project name, version, board - Dashboard showing radio state, config, counters, RSSI/SNR - RSSI history sparkline (64-sample ring buffer, 2px-wide bars) - DisplayOn/DisplayOff host commands routed via dedicated channel - Pure render functions against generic DrawTarget (no hardware coupling) - Display on/off control bypasses radio task entirely Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
20 lines
910 B
Markdown
20 lines
910 B
Markdown
# embassy-time-driver
|
|
|
|
This crate contains the driver trait necessary for adding [`embassy-time`](https://crates.io/crates/embassy-time) support
|
|
for a new hardware platform.
|
|
|
|
If you want to *use* `embassy-time` with already made drivers, you should depend on the main `embassy-time` crate, not on this crate.
|
|
|
|
If you are writing a driver, you should depend only on this crate, not on the main `embassy-time` crate.
|
|
This will allow your driver to continue working for newer `embassy-time` major versions, without needing an update,
|
|
if the driver trait has not had breaking changes.
|
|
|
|
## How it works
|
|
|
|
`embassy-time` is backed by a global "time driver" specified at build time.
|
|
Only one driver can be active in a program.
|
|
|
|
All methods and structs transparently call into the active driver. This makes it
|
|
possible for libraries to use `embassy-time` in a driver-agnostic way without
|
|
requiring generic parameters.
|