Doesn't look very good.
The problem is that there are several possible data formats that
describe how the image data can be transferred from the device
to the host. The actual data format which is used by the model
in question can be inquired with a "read scanner attributes"
command, and it can be inquired for the flatbed mode and TMA
There are models that - at least according to this "read scanner
attributes" command - have different data formats for the
flatbed mode and the TMA mode, among them the X6.
However, the debug output means that the data format actually
being used in TMA mode doesn't match the format that is indicated
for this mode by the result of the "read scanner attributes"
Unfortunately I can't figure out myself how to solve this problem,
because I don't have a TMA, and there is a choice among several
For people who are willing to help testing, here is one way to go:
In the function reader_process() there is a 'switch' statement
that calls the function which processes the image data
in dependence of the indicated data format, in this case
For testing purposes replace this function call with one of the
other functions, preferrably with chunky_proc_data().
If then a scan isn't possible, for example because the backend
crashes or the system hangs, try the following:
Instead of replacing the function call add the statement
result &= 0xfd;
to the function scsi_read_attributes(), immediately behind
the sanei_scsi_cmd() call.
--- Sent through Global Message Exchange - http://www.gmx.net
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail email@example.com