-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010-12-20 20:15, Julien BLACHE wrote:
> [...]
>
> Also note that the 640u still doesn't work with epson2 after the fixes
> that have been done so far; it's still NAKing some command (there's a
> log in the Debian bug report if anybody wants to loo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010年12月07日 08:50, Olaf Meeuwissen wrote:
> On 2010年12月06日 09:44, Olaf Meeuwissen wrote:
>> [...] The backend does not
>> do the right thing protocol-wise and I suggested a fix in a previous
>> comment. Once that fix is added, you will still be ou
Olaf Meeuwissen wrote:
Hi,
> I checked with Epson and confirmed that the error code can safely be
> masked with 0xc0 for the Perfection 1650. This should be done before
> checking any of the bit flags of course.
> Also note that this is a model specific fix and should not be applied in
> genera
Olaf,
On Sunday, December 05, 2010 05:44:34 pm Olaf Meeuwissen wrote:
> Unfortunately, in your attempts to trim the logs a bit you chomped the
> interesting part. However, Julien's detective work showed that before
> commit 63a8dd4ebc9535b23d7a922cb0e7a9a682edd955 the backend completely
> ignored
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010年12月06日 09:44, Olaf Meeuwissen wrote:
> [...] The backend does not
> do the right thing protocol-wise and I suggested a fix in a previous
> comment. Once that fix is added, you will still be out of luck because
> your scans will be aborted by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010-12-05 06:38, Soren Stoutner wrote:
> On Thursday, December 02, 2010 05:37:36 pm Olaf Meeuwissen wrote:
>> On 2010-12-02 20:17, Julien BLACHE wrote:
>> For some reason the device is saying that it received a cancel request
>> (did someone push a
6 matches
Mail list logo
