#display #framebuffer #pixelbuffer

no-std embedded-display-controller

Traits for display controllers

2 unstable releases

0.2.0 Jan 17, 2024
0.1.0 Jan 1, 2021

#272 in Embedded development

Download history 625/week @ 2023-12-23 544/week @ 2023-12-30 687/week @ 2024-01-06 985/week @ 2024-01-13 1101/week @ 2024-01-20 1159/week @ 2024-01-27 1399/week @ 2024-02-03 960/week @ 2024-02-10 829/week @ 2024-02-17 1254/week @ 2024-02-24 1484/week @ 2024-03-02 1478/week @ 2024-03-09 2357/week @ 2024-03-16 2482/week @ 2024-03-23 2153/week @ 2024-03-30 2191/week @ 2024-04-06

9,430 downloads per month
Used in 2 crates

MIT/Apache

9KB
81 lines

Documentation

embedded-display-controller

docs.rs Crates.io

Traits for display controllers

This crate contains traits that represent display controllers with a memory-backed framebuffer. These controllers are typically integrated into a System on Chip (SoC) or connected via a memory bus. They are used to drive larger / higher performance displays.

Note that this crate is not aimed at smaller displays that are updated by sending commands over a low-speed databus (SPI, I2C, ..). These typically have individual driver crates (some examples are listed here). Also note that this crate does not cover functionality available through the panel's own line drivers or management controller. Only the controller in the SoC.

This crate allows libraries for operating on display layers to be written independently of the exact controller architecture.

No runtime deps