[sane-devel] mustek_pp trouble (was: saned doesn't release the parallel port when finished)

[Henning Meier-Geinitz]

Hi,

On Fri, Dec 26, 2003 at 04:22:18PM -0000, Jim George wrote:
> I don't understand what's happening here :(  I checked the connection of
> the scanner on the parallel port and then re-did the scanimage with
> SANE_DEBUG_MUSTEK_PP=255 (I didn't use SANE_DEBUG_SANEI_PA4S2=255 because
> it filled my disk up!).  The result is attached.
> 
> What's wierd is that all the file appears to say that it returned the
> scanner never released.

These are the last few lines:

[saned] process_request: waiting for request
[saned] process_request: got request 3
[mustek_pp] sane_close: maybe waiting for lamp...
[mustek_pp] cis_close: resetting device.
[mustek_pp] cis_reset_device: resetting device
[mustek_pp] cis_set_dpi_value: dpi: 300 -> value 0x20
[mustek_pp] cis_config_ccd: Skip count: 67 (x32)
[mustek_pp] cis_config_ccd: skipcount: 12 imagebytes: 0
[mustek_pp] cis_config_ccd: adjust skip: 0 bytecount: 3
[mustek_pp] cis_return_home: returning home; nowait: 1
[mustek_pp] cis_set_dpi_value: dpi: 300 -> value 0x20
[mustek_pp] cis_config_ccd: Skip count: 67 (x32)
[mustek_pp] cis_config_ccd: skipcount: 12 imagebytes: 0
[mustek_pp] cis_config_ccd: adjust skip: 0 bytecount: 3

So either the mustek_pp backend is in an endless loop here or it
exited for some reason. If it were in an endless loop, saned wouldn't
exit (but it does, doesn't it?). You don't get a segmantation fault
after saned has exited?

Ok, let's look at the code. I'm a bit surprised about the name of that
function (cis_config_ccd) :-) 

So the exit/freeze/whatever happens in cis_config_ccd or
cis_return_home.

Maybe Jochen Eisinger or Eddy De Greef (the authors of that backend)
have any clues on what's going on? 

Bye,
  Henning