Re: [PARPORT] parport_pc_epp_write broken?

From: Tim Waugh (twaugh@redhat.com)
Date: Fri Aug 09 2002 - 10:21:01 EDT

  • Next message: Max Vorobiev: "Re: [PARPORT] parport_pc_epp_write broken?"

    On Fri, Aug 09, 2002 at 03:21:51PM +0200, stef wrote:

    > I've noticed that my parallel port scanner (umax_pp SANE
    > backend) has troubles with 2.4.19, but no problem at all with
    > 2.4.18. Both kernels are built with the same .config.

    Hm. I can't see any changes between 2.4.18 and 2.4.19 that would
    affect only EPP hardware transfers (and not software-emulated EPP
    transfers, which seem to be working fine).

    > It seems that when doing EPP read (using ppdev) some data are
    > losts, and some subsequent reads seem to give part of these datas.

    Odd. How about when software-emulated EPP is used? (You can use
    IEEE1284_MODE_EPPSWE instead of IEEE1284_MODE_EPP.)

    > But the scanner is mostly working doing epp read and write
    > trough ppdev. I've tried to throw parport code from 2.4.18 into
    > 2.4.19, but it showed the same bug. I'll retry this to check I have
    > done it right.

    Okay. Let me know what you find.

    Thanks,
    Tim.
    */



    -- To unsubscribe, send mail to: linux-parport-request@torque.net --
    -- with the single word "unsubscribe" in the body of the message. --



    This archive was generated by hypermail 2b29 : Fri Aug 09 2002 - 10:22:27 EDT