The Canon PIXMA MX850 (and other printers from Canon it seems) have an ethernet port, but do not support any standard network printing protocol, therefore they are not supported in cups out of the box. The protocol used is called BJNP, and uses tcp/udp ports 8611 to 8614.
Fortunately, an open source BJNP driver for cups has been written. You'll find it here, along with install instructions: http://www.fazant.net/cups/.
Once you have BJNP support in Cups, your printer should be auto-detected. You'll be able to print using the Gutenprint PIXMA iP5300 driver.
The following sources provided useful information to me:
ch341.c implements a serial port driver for the Winchiphead CH341.
The CH341 device can be used to implement an RS232 asynchronous serial port, an IEEE-1284 parallel printer port or a memory-like interface. In all cases the CH341 supports an I2C interface as well. This driver only supports the asynchronous serial interface.
My Nokia phones can do it, so I thought there must be a way to do it on my laptop too. I wanted a way to scan both "traditional" barcodes and "two-dimensional" ones, like the QR-Codes. Here is my solution.
You'll need :
- a v4l-compatible webcam + mplayer compiled with v4l support (or any other scriptable way to grab frames from the webcam)
- a scriptable image viewer, I use feh on my laptop
I wanted to try the new 2.6.25 kernel on a Sunblade 100 I'm reinstalling. But immediately after entering "make" I got the following error:
arch/sparc64/kernel/asm-offsets.c:1: error: -m64 is not supported by this configuration arch/sparc64/kernel/asm-offsets.c:1: error: -mlong-double-64 not allowed with -m64 arch/sparc64/kernel/asm-offsets.c:1: error: -mcmodel= is not supported on 32 bit systems make[1]: *** [arch/sparc64/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2
I found the solution here, along with the explanation. To make it short, to get it to work, for now you'll have to type:
It seems that after having been up for a couple of days, the WAG200G starts having issues routing UDP packets properly. This particularly affects VoIP traffic (here IAX2 on port 4569). The symptoms are that "regular surfing" works flawlessly, but the registration with the asterisk server fails. tcpdump shows no traffic on the server side. Restarting the WAG200G immediately solves the problem.
Here is how I restarted the router from the command line: