3 ms·

Sad to see that on "hacker" news the top-post is essentially, go to kinkos. I am legitimately interested in the understanding the scope of the work and what it

Sad to see that on "hacker" news the top-post is essentially, go to kinkos. I am legitimately interested in the understanding the scope of the work and what it would entail to solve such a problem successfully. And, maybe I only have enough resources to solve the elementary steps but that's beside the point. Also, this is a relatively new post so maybe relevant information will eventually bubble up. I am starting to see some interesting comments.

pessimizer 4y ago
> Sad to see that on "hacker" news the top-post is essentially, go to kinkos. "Essentially" is essentially dishonest here. The top post says: 1. HN is not the best venue to get help for this. 2. The answers that you have gotten so far are mostly bad. 3. Printer drivers in Linux almost never involve a custom kernel driver. 4. The Arch Linux forums would be better for this question. 5. Running the 32 bit driver might be easier than writing a 64 bit driver. 6. You might need some packaging help to run the 32 bit driver on a 64 bit system. 7. This would probably only be a worthwhile project only if you were trying to learn, because there are easier ways to get the printer to work. 8. What's coming over the wire will probably be proprietary and obfuscated. 9. Figuring out Canon's format with wireshark output will be very difficult, even for someone with experience at writing drivers. It also inspired a comment from jrockway that offers additional practical, experienced advice. ---- What I can't figure out is what you're offering other than your approval and disapproval of what other people are doing. There's maybe one more comment on this entire thread, recently submitted, that offers more information than the one you're criticizing.