I've had a look at building ppbus, taken from SF CVS today, on a NetBSD 2.0 machine (No -current at hand).
There were some problems with taking out stuff from the files that isn't in 2.0. But this was just misc stuff, unreleated to ppbus.
Another problem was that the code didn't seem to be very clean. Did you hack the kernel build framework to remove the -Werror from CFLAGS? After sprinkling some =0 to initialize variables I was fed up and didn't want to handle the rest of the problems, including some not-so-trivial ones, so I put a -Wno-error in there. I hope that the thing still built correctly, couldn't look at the remaining warnings because they scrolled out and I forgot to redirect them before.
About the operation of the driver:
It seems that only the standard mode with ieee=off works. The other modes didn't produce output. There was one exception: Once, I think with fast mode, I got two partial lines of output. They looked like the ink has finally run out, so I replaced it. Later I got some more garbage printed and noticed that only the color ink was empty and the black tank was still half full. This is great... I've sealed it and put it in the cabinet to see if it can be used later (much later, given my current print volume).
On a closer look it turned out that there were a few lines missing between the two partial lines printed before changing the ink. Seems some data was lost. With the other modes the LED at the printer usually blinked as it does normally, but nothing else happened. This is usually a sign that the printer can't understand the data it receives.
I have to admit that bidirectional communication isn't possible with my setup, because I use a simple unidirectional autoswitchbox. However, when I boot Windows it prints fine. It claims to use ECP, but I don't know if it automatically falls back to standard mode when "bidirectional support" is disabled. This was necessary to get it print over the box.
I've also tried to connect the printer directly, without the box. However I think that the cable could now be the limiting factor. It's really old and I'm not sure if it has all the necessary wires for bidirectional modes. I'm going to try again with a newer one which should be correct.
Does the ECP mode always need a bidirectional connection, even for simple jobs such as printing?
I'm happy to try further patches (if they compile in a reasonable amount of time).
Log in to post a comment.