Arch package maintainer here; we generally encourage building from source for packages provided by the official repositories. As far as I know, we only ship pre compiled binaries if there is no source available, i.e. commercial programs such as reaper.
I just glanced, they still want about 500 bucks for the 13" screen and half of that for the board to drive it. While I have no clue what making the screen at a low scale might cost, the board cannot possibly be five times more expensive than a Raspberry Pi, can it?
No, simple driver boards aren't super complicated. Nor are the chips on them manufactured on the fanciest nodes. They're not super-high-volume either though and as a result somewhat expensive on a BoM.
It's basically a fairly simple SPI interface (or here a SPI wrapper around an internal Z80 protocol). The rest of the board is power supply handling and a DRAM framebuffer chip, external to the driver ASIC on SPI as well. I wrote a custom driver for this in Rust for my project, and it only took about a day despite a few leaky-abstractions oddities in how it communicates over SPI.
The chip itself is basically buffer handling, image processing (features like JPEG decode, resampling and some LUT mechanisms) and a waveform generator. Others will have some IP blocks for, say, a HDMI frontend. Any decent chip company can crank this out pretty quick. There's easily 10+ product lines on the market.
For simple things you may not even need one and can drive the panel from an MCU directly.
There are more expensive, more advanced drivers that implement more complicated and higher-performance (say, refresh rate) update schemes or I/O though.
Realistically you’re not paying for the hardware when you buy the driver board, but rather the software baked into those boards.
The waveforms, and the algorithms that create waveforms, used to drive eInk displays at reasonable speeds and produce high quality images are highly proprietary and very difficult to develop. In theory it’s easy to make an eInk display an image, but doing that in a reasonable period of time, when transitioning from potentially any starting state, and handling the crosstalk between pixels, makes creating good images on an eInk display pretty hard to get right.
Apple (and other streaming services) have been caught out replacing people’s local songs with censored/blessed versions. That is the main reason why some characters will not stream music; because they do not have full control over their own files.
Why is streaming mutually exclusive with owning local copies? My girlfriend has Spotify, I have Apple Music. We also have an extensive FLAC collection of our “forever artists”.
Does anyone know how to access any of the repos listed in this vault? I’m after a particular one that was deleted earlier this year; has zero forks and does not show up in the way back machine.
I don’t know what I would do without sieve, I use it to manage my mailing list subscriptions, eg move to folders, mark emails from specific chatty users as read, etc.
It automates a lot of manual cruft and I’m endlessly thankful for it.
I do wish it was more widely supported, and I try to do my part to encourage adoption (I maintain several sieve related packages for Arch Linux).
No, I just followed the instructions, I was wondering if I should make one.
I also had the problem, but that is something for which you just need to run with sudo. Maybe there's a way to configure the path so that it can be run as an unprivileged user?
reply