--FL5UXtIhxfXey3p5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Here is a good patch (I did an extensive set of tests to make
sure it is working as intended)
Varol
On Tue, Nov 04, 2003 at 03:47:43PM -0500, k...@khk.net wrote:
> You basically disabled the error checks f
Sorry, you are partially right. I do have to make sure that the extra
lines added no not go beyond the physical limits of the device.
The piece of code removed from the sane_get_parameters() function,
though is never executed - sane_get_paramters() is executed before
s->hw->color_shuffle is actual
You basically disabled the error checks for a negative number of
scan lines and the case where more scan lines as the scanner can support
are requested. This is not acceptable - the checks are there for
a reason. You are certainly free to use a modified backend with
your scanner, but I will not app
--1yeeQ81UyVL57Vl7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Here is a patch that fixes color scanning on the EPSON Perfection610. It is
based on the epkowa backend (but done in a cleaner way). It works for me -
and most probably does not break anything else. Can peopl
Hi,
On Mon, Nov 03, 2003 at 04:34:45AM -0500, Varol Kaptan wrote:
> The second problem I have is the following: It seems like the epson
> scanners can only scan areas with a width which is a multiple of 8.
> When I scan a 1in x 1in area at 600 dpi I get a 600x600 ppm (that's
> fine). When I scan t
Hi everybody,
First, I would like to report a problem with the epson backend on a
Perfection610. As far as I can see the color scanning for this scanner
has been screwed for some time now (including the latest 1.0.13-pre1).
This problem goes back to 1.0.9 (at least - probably much earlier).
Color