From what I've gathered, *the* way do efficiently connect a (larger, e.g. 5" 3rd party - the officiel 7" is too large) display to the Pi is via HDMI, correct?
So I've been looking around and found a seemingly suitable touch display. I assume the touch stuff needs extra eonnections beside HDMI?
(I aim to use a RasPi zero for this)
My aim is to build a system that boots up as fast as possible (single digit seconds, preferably low), so I'd try to make a Buildroot based image with only necessary stuff.
And now I wonder - since the device shall only run the custom application, in full possession of the screen, it might be nice to get rid of all the desktop server stuff, too.
Is it possible to do that? I have no idea how one would access such a display without a running desktop, and then link Qt lib or something.
I'd basically be happy if some driver allowed me to throw frame buffer contents at the display (using some platform-agnostic gfx libs that wants a pixel buffer) and get the touch information.
Is that possible, and how involved is that?
So I've been looking around and found a seemingly suitable touch display. I assume the touch stuff needs extra eonnections beside HDMI?
(I aim to use a RasPi zero for this)
My aim is to build a system that boots up as fast as possible (single digit seconds, preferably low), so I'd try to make a Buildroot based image with only necessary stuff.
And now I wonder - since the device shall only run the custom application, in full possession of the screen, it might be nice to get rid of all the desktop server stuff, too.
Is it possible to do that? I have no idea how one would access such a display without a running desktop, and then link Qt lib or something.
I'd basically be happy if some driver allowed me to throw frame buffer contents at the display (using some platform-agnostic gfx libs that wants a pixel buffer) and get the touch information.
Is that possible, and how involved is that?
Statistics: Posted by tryingthepi — Thu May 09, 2024 4:59 pm — Replies 1 — Views 12