Introduced a couple of CAP defines PIXMA_CAP_SCAN_FULL_WIDTH_ADF and
PIXMA_CAP_SCAN_FULL_WIDTH_FLATBED to specify machines that have a buggy
width selection implementation. The imageClass MF4770n has problems
on the ADF with certain width selections. We will scan the entire width
of the media and crop out what we don't want.
These are computed values for the coming scan and they are prefixed with
be_ and fe_ for frontend and backend respectively.
"frontend" here means what the user requests, and "backend" means what
we are asking of the scanner. This is mostly the same, but when doing
lineart, the backend is actually doing grey, since lineart is not
directly supported.
Many of the bugs here are related to the incorrect use of the fe_ values
when communicating with the scanner during the scan and it completely
messes up our processing of the raw scan data. The separation makes it
clearer what the parameters refer to.
This concludes the support for the MX492 which is now fully functional.
Enable autofocus support on my Epson 12000XL. The middle of the scan
area will be used as the focus point. An arbitrary X,Y is possible but
not implemented yet
Signed-off-by: Wolfram Sang <wsa@kernel.org>
Allow the whole range of manual focus settings as an expert option. This
is also now independent of a TPU being installed or not. The old default
values are applied if the user changes the source type (either FLATBED
or TPU). Adding a focus group here because autofocus options will come
with later patches.
Signed-off-by: Wolfram Sang <wsa@kernel.org>
coolscan2 has focus entries already reused in coolscan3. Because I want
to add the same options to epson2, it makes sense to make them available
globally. Add i18n while here.
Signed-off-by: Wolfram Sang <wsa@kernel.org>
Even with USB based scanners, we need to send the esci command to set
the focus. There is no byte in the extended scanning parameters for it.
So, move the code to a place where it is called for all cases.
Signed-off-by: Wolfram Sang <wsa@kernel.org>
- restructure fine calibration code
- initial support for uploading fine calibration payloads
- improve DR-C225 support
Most canon scanners require that the driver apply fine (per-cell)
calibration information. But a few require that the info be loaded
into the scanner. Here, we add initial support for that, though the
needed values are hardcoded instead of calculated.
On many systems now python executable it is python3.
On my system it the case and by this muild failed with:
make[2]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/backends-1.0.31/backend'
make[2]: Entering directory '/home/tkloczko/rpmbuild/BUILD/backends-1.0.31/backend'
Generating pixma/pixma_sane_options.h from pixma/pixma.c
/bin/sh: python: command not found
make[2]: *** [Makefile:7317: pixma/pixma_sane_options.h] Error 127
make[2]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/backends-1.0.31/backend'
make[2]: *** Waiting for unfinished jobs....
Using AM_PROG_PYTHON() nmacro cllows avoide tha by hecks current version of the
python and allw to use custom python executable by execute configure by:
$ PYTHON=</some/python> ./configure <params>
AM_PROG_PYTHON aclocal macro propagates to automake files $(PYTHON) variable
which could be used on geberate instaleable scripts on duting build process like
it is now in backend/Makefile.am.
Currently minum version of required vesion of the python is python >= 3.
Now that we no longer include generated files in our git repository
builds should always have maintainer mode enabled so checkouts pick
up on changes in Makefile.am, configure.ac, etc. between builds.
See #350.
Will shortly refacture image_size, line_size and other scan parameters
to be able to differentiate between our interactions with the scanner
and the user, because these value might be different such as in the
case of software_lineart where the user is getting lineart, but the
scanner is giving us grey. The difference in the values of these
critical parameters is what is causing most of the issues.
Ralph Little