Michal Sabala <[EMAIL PROTECTED]> wrote:
Hi,
> Following is the part of epson.c driver that fails, in my case, buf[0]
> contains 0xb0. Original poster also had 0xb0 in the beginning of the 88
> byte buffer.
>
> 06144 receive (s, buf, len, &status); /* reveive actual status
> data */
> 06145
> 06146 if (buf[0] & 0x80)
> 06147 {
> 06148 close_scanner (s);
> 06149 return SANE_STATUS_INVAL;
> 06150 }
>
> The check fails. What is the meaning of 0x80? How about 0xb0? Could
> it be talking to the printer??? (CX5200 is a scanner/printer
> device).
Well I don't know :) Those magic numbers probably come from the
reverse-engineering of the protocol...
I'll have to take a deeper look at the problem, maybe it's been fixed
already but I don't know.
I'm a bit low on time right now, I'll try to get back to you on that
early next year.
Thanks,
JB.
--
Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]>
Public key available on <http://www.jblache.org> - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
