Re: Drivers on ARM architecture
If the driver makes only common system calls and is not written to be architecture-specific, then compiling from source should work. However, too many drivers are architecture-specific because that is an easy way to squeeze out additional performance. Also, many so-called "sources" are not actually source code but just a script that compiles a source wrapper with proprietary firmware blobs. This is almost always the case with WIFI chipsets, offbeat NICs, FakeRAID cards and especially video drivers. If so, then the blobs were likely compiled for x86/_64 and won't work with ARM. It is impossible to tell in the Epson case without going over the code, which I am not remotely qualified to do. But since printers are relatively simple peripherals, you have a fighting chance that the "source" code is true source and may work.
Originally Posted by only.tiki
This ignores the larger issue that compiling from source is not an exercise recommended for absolute beginners. You need at least a rudimentary understanding of how the system works, and what packages are needed for a proper compilation. There are guides all over the internet and it's not really all that hard once you get the hang of it, but it is frustrating at the start.
In my opinion, the best strategy for your situation is to find a driver from the repository that provides most of the functionality that you need. Often, drivers for older printer models will still work with newer models. I don't own any Epson printers, so can't help with which might be good candidates. As always, experimentation can provide a quick confirmation.
Newb: How far must I jump to clear the ledge halfway down?
Guru: It's bad to jump off cliffs. Let's look at better options.
Newb: Stop harping about "best practices" and just tell me.