I really like epaper displays for all of the reasons mentioned in the article. Shame the patent locks continue to keep prices high even though the core technology has improved enough for prices to drop.
A few years ago I came into a couple of e-ink displays that had been previously used for storefront/product pricing. The hardware to drive them was locked down but I was able to reverse engineer the panel by finding a datasheet that was close enough and hacking up an adafruit thinkink. I had a lot of fun writing my own driver/abstraction layer. I originally intended to support a bunch of different panels but ran out of steam after the first one did exactly what I wanted.
Glad I wasn’t the only one who thought this. The post is also missing one obvious thing that I expect in any technical post: code snippets. Let me see the code.
ChatGPT has ruined bullet points for the rest of us…
No offense but writing this blog post couldn’t take more than a few minutes, why spoil it with LLM? Shoot, use one to check grammar and recommend edits even.
Ah yes, one of my favorite skills learned in school was how to work around arbitrary rules made up by cranky sysadmins! I still use it all the time.
The smart kids (whom I’m sure look like they are learning that precious openssh client) are doing their assignment locally or on a free tier VPS with VS Code and scping the thing over when it’s done.
They’re also smart enough to learn openssh when they need it IRL.
I came here to say this. I haven’t worked with the Elite X but the past gen stuff I’ve used (865 mostly) the accelerators - compute DSP and much smaller NPU - required _very_ specific setup, compilation with a bespoke toolchain, and communication via RPC to name a few.
I would hope the NPU on Elite X is easier to get to considering the whole copilot+ thing, but I bring this up mainly to make the point that I doubt it’s just as easy as “run general purpose model, expect it to magically teleport onto the NPU”.
A few years ago I came into a couple of e-ink displays that had been previously used for storefront/product pricing. The hardware to drive them was locked down but I was able to reverse engineer the panel by finding a datasheet that was close enough and hacking up an adafruit thinkink. I had a lot of fun writing my own driver/abstraction layer. I originally intended to support a bunch of different panels but ran out of steam after the first one did exactly what I wanted.
https://github.com/jaygreco/MagInkCal