|
|
|
|
|
by dragontamer
286 days ago
|
|
Thanks. That article seems to have the quote I was looking for. > E-ink screens are quite power hungry when it comes to peak current. Modern high-resolution panels can consume >20 W peak. This is where I was wondering and yeah, 20+W is pretty hefty to support a relatively small 8" EInk screen or something. All those updates cost all that power as long as updates are occurring. Maybe you can optimize many of them away (if some parts of the screen don't move, especially if software was rewritten to optimize for the display). More importantly, it sounds like you've created a full custom FPGA controller over the voltages that go into an EInk display? That's impressive in its own right even if I don't think 75Hz is a good idea lol. -------- FPGA or Full Blown Microprocessor are the only choices here. A high power SIMD/NEON arm64 probably could do the job, but I think the Spartan6 is a good choice as well and has more obvious and straightforward parallelism (and probably all the pins required to control the screen. Even a big microprocessor won't have as many low latency pins as an FPGA). |
|
Yes, that’s definitely something we want to work toward. As the community grows, we hope to tackle these kinds of optimizations together.
> A high power SIMD/NEON arm64 probably could do the job, but I think the Spartan6 is a good choice as well and has more obvious and straightforward parallelism
Yes, precisely for the reasons you stated. We also talk more about it below:
- https://www.youtube.com/live/okjJURIejIY
- https://github.com/Modos-Labs/Glider?tab=readme-ov-file#desi...