Yep, after having a look at the log file you sent, messages look very
similar to MP730 series ones, so it should be a good start point.
What might be more uncertain is the ADF management, this is a bit weak
in the pixma backend.
Depending on modifications you add, you need to figure out if it cou
Hi,
Currently maintaining the pixma backend, I can give you tips and
knowledge on it if you want to design a backend for those Canon MFPs.
Especially if the protocol used by them is similar to the PIXMA
protocol, then it can be easy to integrate them either in the pixma
backend (the easiest, let
Guillaume Gastebois schrieb:
> Hello,
>
> Me again !
>
> I'm trying to find what are GPIO14,13,12 and 11 for.
>
> I find GPIO11=home switch and must be 0.
> I thought I found GPIO14 was half CCD but by adding :
> /* gpio part. here: for canon lide 90 */
> if (dev->model->gpo_type == GPO_CANONLID
arly symmetrical to the diagonal axis, meaning
two consecutive bytes are uncorrelated. The result of the white part
shows a larger band, typical around 20 pixels width, but with a lot of
speckles(which is in no way an indicator of problems).
Regards,
Pierre
-- next part ---
Hello,
Me again !
I'm trying to find what are GPIO14,13,12 and 11 for.
I find GPIO11=home switch and must be 0.
I thought I found GPIO14 was half CCD but by adding :
/* gpio part. here: for canon lide 90 */
if (dev->model->gpo_type == GPO_CANONLIDE90)
{
r = sanei_genesys_get_address (reg, 0x6c);
I dug around some more and I think I've decoded most of the commands and
protocols. Of the 3 pixma subfamilies, it most closely resembles the mp730.c
code. Lamp/calibration/busy flags seem to be moved around a little but the
has-paper flag seems the same (on a side note, I have yet to observe
