Re: [SnapScan] Core testing group

From: Timothy Little (tim@lilly-villa.little-possums.net)
Date: Tue Oct 10 2000 - 15:13:28 PDT

  • Next message: Joachim Ansorg: "Sane with latest Gimp"

    On Tue, Oct 10, 2000 at 10:29:06AM -0400, cbagwell@sprynet.com wrote:
     
    > The main thing I want to work on is getting USB support integrated
    >fully into the scanscan driver so that its a config file option
    >instead of a compile time option. I'll also be happy to test
    >anything others develop to make sure it works with a 640BU.

    Yes, I'd like that too. It seems strange that USB is mutually
    exclusive at compile-time with SCSI.

    My Agfa Snapscan 1212U mostly works now. I only get the occasional
    permanent lock-up of SANE and the scanner now. It scans at all tested
    resolutions in colour, though I haven't tried gey-scale yet or any of
    the other fancy options. It *really* did not like it when I tried to
    scan at 300 dpi and forgot to remove the "preview" option from the
    command-line.

    I'd still like to find the conditions under which it locks up, and
    find a way of resetting it without rebooting.

    > Oh yeah, and if SANE tries to ever scan the system to see whats out
    > their and access /dev/scanner then it actually passes a USB bulk_msg
    > call which locks up the kernel scanner.o driver and then SANE and
    > makes them both unusable.

    Ah, maybe that's the cause of the lockup. What is a USB bulk_msg? Do
    you know why it locks up the kernel driver? "scanimage -T" seems to
    work OK most of the time, it's only when a previous operation failed
    that it locks up.
     
    - Tim

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
    



    This archive was generated by hypermail 2b29 : Tue Oct 10 2000 - 15:06:53 PDT