[sane-devel] Re: Sane-devel digest, Vol 1 #397 - 14 msgs
Nicholas Robinson
npr at bottlehall.freeserve.co.uk
Thu Apr 10 17:34:46 BST 2003
It was the v1.0.8 backends that were causing the problem. Sorry about that - I
had realised that the backends were not the most recent version but thought
that because sane0find-scanner was working that it must be more frontend!
On Thursday 10 Apr 2003 10:29 am, sane-devel-request at www.mostang.com wrote:
> Send Sane-devel mailing list submissions to
> sane-devel at www.mostang.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.mostang.com/mailman/listinfo/sane-devel
> or, via email, send a message with subject or body 'help' to
> sane-devel-request at www.mostang.com
>
> You can reach the person managing the list at
> sane-devel-admin at www.mostang.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Sane-devel digest..."
>
>
> Today's Topics:
>
> 1. Hai, about probe_scanner can't be probed (Fan Dan)
> 2. Fwd: Problems after upgrading to Redhat 8.0 (Nicholas Robinson)
> 3. Re: Fwd: Problems after upgrading to Redhat 8.0 (Henning
> Meier-Geinitz) 4. HP7400 on usb (Ondrej Koala Vacha)
> 5. Re: HP7400 on usb (Henning Meier-Geinitz)
> 6. Re: SCSI device running on Darwin (mindfuq at comcast.net)
> 7. Re: XSane-0.90 released (Tim Waugh)
> 8. Problems with CX-3200 (Tyler Montbriand)
> 9. Re: Problems with CX-3200 (Karl Heinz Kremer)
> 10. Compile problem in 1.0.11 (John Coppens)
> 11. No devices found with mustek III ep plus (Donald Quaid)
> 12. RE: No devices found with mustek III ep plus (edg1 at tiscali.be)
> 13. Re: Compile problem in 1.0.11 (Henning Meier-Geinitz)
> 14. Re: Hai, about probe_scanner can't be probed (Henning Meier-Geinitz)
>
> --__--__--
>
> Message: 1
> From: "Fan Dan" <dan_fancn at hotmail.com>
> To: sane-devel at www.mostang.com
> Date: Tue, 08 Apr 2003 22:41:33 +0800
> Subject: [sane-devel] Hai, about probe_scanner can't be probed
>
> Hai, Henning
>
> Today, I modified scanner.c for Mustek A3Pro usb scanner (0x055f
> 0x0401)
> In probe_scanner.
> modified
> have_bulk_in = 1
> have_bulk_out =2
> have_intr = 3
> to
> have_bulk_in = 0
> have_bulk_out = 1
> have_bulk_intr = 2
>
> /////////////////////////////////////////
> + have_bulk_in--
> + have_bulk_out--
> + have_intr--
> if (!(scn = kmalloc (sizeof (struct scn_usb_data), GFP_KERNEL))) {
> err("probe_scanner: Out of memory.");
> up(&scn_mutex);
> return NULL;
> }
> memset (scn, 0, sizeof(struct scn_usb_data));
>
> init_MUTEX(&(scn->sem)); /* Initializes to unlocked */
> /////////////////////////////////////////
>
> then scanner that has three endpoints can be probed successly, because
> maxpacketout[3] = 0, but maxpacketout[2] = 1 in USB module;
>
> And scanner can be writed, but we can't read from that. so I midified some
> code int read_scanner function.
> //////////////////////////////////////////////////////
> - result = usb_bulk_msg(dev, usb_rcvbulkpipe(dev, scn->bulk_in_ep), ibuf,
> this_read, &partial, scn->rd_nak_timeout);
> + result = usb_bulk_msg(dev, usb_rcvbulkpipe(dev, scn->bulk_out_ep), ibuf,
> this_read, &partial, scn->rd_nak_timeout);
> /////////////////////////////////////////////////////
> Then scanner can be write and read.
>
> I have test that we can write some bytes to DRAM of scanner, then read them
> for scanner, that is OK. ioctl also is OK.
>
> I want to know that there are three endpoint in scanner, but why both in
> bulk and out bulk are in same ep? Whether is that OK??
>
> Good Lucky!
>
> Dan
>
> _________________________________________________________________
> ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/cn
>
>
> --__--__--
>
> Message: 2
> From: Nicholas Robinson <npr at bottlehall.freeserve.co.uk>
> Date: Tue, 8 Apr 2003 16:46:09 +0100
> To: sane-devel at www.mostang.com
> Subject: [sane-devel] Fwd: Problems after upgrading to Redhat 8.0
>
>
>
> ---------- Forwarded Message ----------
>
> Subject: Problems after upgrading to Redhat 8.0
> Date: Sun, 6 Apr 2003 17:01:56 +0100
> From: Nicholas Robinson <npr at bottlehall.freeserve.co.uk>
> To: sane-devel-admin at www.mostang.com
>
> Hi
>
> I've been using sane and xsane with a snapscan 1236 for over a year and
> upgraded a number of times. I usually use xsane across the network and ha=
> ve
> no trouble.
>
> I've just upgraded to RH8.0 and my sane-backends and xsane were 'upgraded=
> '.
>
> I've now got sane-backends 1.0.8 and xsane 0.90-1.
>
> I now can't run xsane either on the local machine with the scanner attach=
> ed
> or across my network. If I do a sane-find-scanner on the local machine a=
> s an
> ordinary user then I can see the device and also through /proc/scsi/scsi=
> =2E
> Whenever I try xsane (or scanimage, xscanimage, etc.) I am told there ar=
> e no
> sane devices available.
>
> Can anyone suggest why this is?
>
> Regards
>
> Nick
>
> -------------------------------------------------------
>
>
> --__--__--
>
> Message: 3
> Date: Tue, 8 Apr 2003 18:47:53 +0200
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: sane-devel at www.mostang.com
> Subject: Re: [sane-devel] Fwd: Problems after upgrading to Redhat 8.0
>
> Hi,
>
> On Tue, Apr 08, 2003 at 04:46:09PM +0100, Nicholas Robinson wrote:
> > I've been using sane and xsane with a snapscan 1236 for over a year and
> > upgraded a number of times. I usually use xsane across the network and
> > have no trouble.
> >
> > I've just upgraded to RH8.0 and my sane-backends and xsane were
> > 'upgraded'.
> >
> > I've now got sane-backends 1.0.8 and xsane 0.90-1.
>
> sane-backends-1.0.8 is pretty old.
>
> > I now can't run xsane either on the local machine with the scanner
> > attached or across my network. If I do a sane-find-scanner on the local
> > machine as an ordinary user then I can see the device and also through
> > /proc/scsi/scsi. Whenever I try xsane (or scanimage, xscanimage, etc.) I
> > am told there are no sane devices available.
> >
> > Can anyone suggest why this is?
>
> Is "snapscan" in /etc/sane.d/dll.conf? If yes, what's the output of
> SANE_DEBUG_SNAPSCAN=255 scanimage -L
>
> Bye,
> Henning
>
> --__--__--
>
> Message: 4
> Date: Tue, 8 Apr 2003 22:02:19 +0200 (CEST)
> From: Ondrej Koala Vacha <koala at fi.muni.cz>
> To: <sane-devel at www.mostang.com>
> Subject: [sane-devel] HP7400 on usb
>
>
>
> Hi,
>
> I do have scanner HP ScanJet 7450 (it is 7400 with ADF),
> Linux Redhat 7.2, kernel 2.4.20 with modules usbcore, uhci
> compiled myself.
> I have downloaded sane version
> sane-avision-2003-03-27-0055-build70.tar.bz2
> and compiled with no warnings.
>
> usb modules:
>
> usbcore
> uhci
>
> and mounted
> none /proc/bus/usb usbdevfs defaults 0 0
>
>
> them after setting
> export AVISION_DEBUG=8
> scanimage -L
>
>
> gives
> ...
> [avision] sane_init: parsing config line "usb /dev/usbscanner0"
> [avision] sane_init: config file line 18: trying to attach USB:`usb
> /dev/usbscanner0' [avision] sane_init: parsing config line "usb
> /dev/usb/scanner0"
> [avision] sane_init: config file line 19: trying to attach USB:`usb
> /dev/usb/scanner0' [avision] sane_init: parsing config line ""
> [avision] sane_init: config file line 20: ignoring empty line
> [avision] sane_init: parsing config line "usb 0x03f0 0x0801"
> [avision] sane_init: config file line 21: trying to attach USB:`usb 0x03f0
> 0x0801' [avision] sane_init: parsing config line ""
> ...
>
> No scanners were identified etc.
>
>
> What am I doing wrong?
>
> Thank you
>
> Ondrej Koala Vacha
>
>
>
> --__--__--
>
> Message: 5
> Date: Tue, 8 Apr 2003 23:34:16 +0200
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: sane-devel at www.mostang.com
> Subject: Re: [sane-devel] HP7400 on usb
>
> Hi,
>
> On Tue, Apr 08, 2003 at 10:02:19PM +0200, Ondrej Koala Vacha wrote:
> > I do have scanner HP ScanJet 7450 (it is 7400 with ADF),
> > Linux Redhat 7.2, kernel 2.4.20 with modules usbcore, uhci
> > compiled myself.
> > I have downloaded sane version
> > sane-avision-2003-03-27-0055-build70.tar.bz2
> > and compiled with no warnings.
>
> Is the scanner listed in /proc/bus/usb/devices? If not, something with
> your kernel USB system is wrong (wrong driver?).
>
> If yes, does sane-find-scanner find the scanner? If it's not found
> even as root, you may not have libusb-0.1.6 or newer. When you build
> sane, configure prints a line like this "Libs=-lusb ...". If the -lusb
> part is not there, libusb was not found. YOu may need to update your
> libusb in this case.
>
> Bye,
> Henning
>
> --__--__--
>
> Message: 6
> Date: Sun, 8 Apr 2001 20:28:58 +0000
> From: mindfuq at comcast.net
> To: sane-devel at www.mostang.com
> Subject: Re: [sane-devel] SCSI device running on Darwin
>
> > The mailing list search engine works quite well for me so what's the
> > problem for you? See http://www.mostang.com/sane/mail.html
>
> Ah, I found it now.. I guess I wasn't expecting it to be on the parent
> page of the archive listings. Sorry about that.
>
> --__--__--
>
> Message: 7
> Date: Wed, 9 Apr 2003 09:31:35 +0100
> From: Tim Waugh <twaugh at redhat.com>
> To: Oliver Rauch <oliver.rauch at rauch-domain.de>
> Cc: sane-devel at mostang.com
> Subject: Re: [sane-devel] XSane-0.90 released
>
>
> --x8hBN3jcr0uqJpm2
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> Hi Oliver,
>
> It would be nice to have a configure option for which browser to use
> for displaying HTML help. Currently 'netscape' seems to be interwoven
> into the source code, and I'm scared to change it. :-)
>
> Tim.
> */
>
> --x8hBN3jcr0uqJpm2
> Content-Type: application/pgp-signature
> Content-Disposition: inline
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQE+k9pjtO8Ac4jnUq4RAn6RAJ0S7sYBbP6N+26ntENTpHqgH5f6JwCgo2rw
> 5ZhhRjL6tXzPl2b+88YkMok=
> =HKuA
> -----END PGP SIGNATURE-----
>
> --x8hBN3jcr0uqJpm2--
>
> --__--__--
>
> Message: 8
> From: Tyler Montbriand <tsm at accesscomm.ca>
> Organization: TSM Computer Interfacing
> To: sane-devel at www.mostang.com
> Date: Wed, 9 Apr 2003 17:03:22 -0600
> Subject: [sane-devel] Problems with CX-3200
>
> Running Mandrake 9.0 with custom kernel
> Kernel: 2.4.21-0.11
> Xsane: 0.87
> libsane: 1.0.8-5
>
> I've managed to get my Epson CX-3200 print/scan/copy device working very =
> well=20
> with Linux, for the most part. Printing through CUPS works fine, and I'v=
> e=20
> finally managed to get SANE configured to use my scanner. How simple it =
> is=20
> when you know how...
>
> As for what driver it's using, 'scanimage -L' gives=20
> 'device `Epson:/dev/usb/scanner0' is a Epson CC-570L scanner' and that wo=
> rks -=20
> for the most part. There is one obnoxious problem, however; when the=20
> scanner decides it needs to warm up for awhile first(the LCD on the front=
> =20
> panel says 'warming up'), Xsane waits awhile, gives an error popup messag=
> e,=20
> then spinlocks(taking 100% cpu) until it's killed. Upon restarting Xsane=
> ,=20
> the scanner's warmed up by now and works again. Is this a known problem?
>
> --__--__--
>
> Message: 9
> Date: Wed, 9 Apr 2003 19:15:24 -0400
> From: Karl Heinz Kremer <khk at khk.net>
> To: Tyler Montbriand <tsm at accesscomm.ca>
> Cc: sane-devel at www.mostang.com
> Subject: Re: [sane-devel] Problems with CX-3200
>
>
> --oyUTqETQ0mS9luUI
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> No, this is not a known problem. Can you try to capture a log file while
> the scanner is warming up? Just run the following commands in a command
> shell (e.g. xterm):
>
> export SANE_DEBUG_EPSON=3D128
> xsane > /tmp/scan.log 2>&1
>
> Let it run for some time, then kill xsane. Then send the log file to me
>
> Thanks,
>
> Karl Heinz
>
> On Wed, Apr 09, 2003 at 05:03:22PM -0600, Tyler Montbriand wrote:
> > Running Mandrake 9.0 with custom kernel
> > Kernel: 2.4.21-0.11
> > Xsane: 0.87
> > libsane: 1.0.8-5
> >=20
> > I've managed to get my Epson CX-3200 print/scan/copy device working very
> > =
>
> well=20
>
> > with Linux, for the most part. Printing through CUPS works fine, and
> > I'v=
>
> e=20
>
> > finally managed to get SANE configured to use my scanner. How simple it
> > =
>
> is=20
>
> > when you know how...
> >=20
> > As for what driver it's using, 'scanimage -L' gives=20
> > 'device `Epson:/dev/usb/scanner0' is a Epson CC-570L scanner' and that
> > wo=
>
> rks -=20
>
> > for the most part. There is one obnoxious problem, however; when the=20
> > scanner decides it needs to warm up for awhile first(the LCD on the
> > front=
>
> =20
>
> > panel says 'warming up'), Xsane waits awhile, gives an error popup
> > messag=
>
> e,=20
>
> > then spinlocks(taking 100% cpu) until it's killed. Upon restarting
> > Xsane=
>
> ,=20
>
> > the scanner's warmed up by now and works again. Is this a known problem?
> > _______________________________________________
> > Sane-devel mailing list
> > Sane-devel at www.mostang.com
> > http://www.mostang.com/mailman/listinfo/sane-devel
>
> --=20
> Karl Heinz Kremer khk at khk.net
> PGP Key at http://www.khk.net/download/khk.asc
> EPSON Sane Backend: http://www.khk.net
>
> --oyUTqETQ0mS9luUI
> Content-Type: application/pgp-signature
> Content-Disposition: inline
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
>
> iD8DBQE+lKmMxejv3RfKrhsRAmZ9AKCQcI9PsfA+261WH52MYOpfDn3E3QCfZUl+
> tymjQOZnJOA4GQLzRnfO+bU=
> =M5WQ
> -----END PGP SIGNATURE-----
>
> --oyUTqETQ0mS9luUI--
>
> --__--__--
>
> Message: 10
> Date: Thu, 10 Apr 2003 00:46:27 -0300
> From: John Coppens <jcoppens at usa.net>
> To: sane-devel at www.mostang.com
> Subject: [sane-devel] Compile problem in 1.0.11
>
> Hi all...
>
> Get this error on compiling sane-backends 1.0.11:
>
> gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include
> -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d
> -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0
> -DBACKEND_NAME=v4l -DLIBDIR=/usr/local/lib/sane v4l.c -fPIC -DPIC -o
> v4l.lo
> In file included from /usr/include/linux/videodev2.h:16,
> from /usr/include/linux/videodev.h:14,
> from v4l.c:76:
> /usr/include/linux/time.h:9: redefinition of `struct timespec'
> /usr/include/linux/time.h:88: redefinition of `struct timeval'
> /usr/include/linux/time.h:93: redefinition of `struct timezone'
> /usr/include/linux/time.h:124: redefinition of `struct itimerval'
>
> In v4l.c, line 67, I changed:
>
> #include <sys/time.h>
> to
> #include <linux/time.h>
>
> which eliminated two errors and left:
>
> In file included from v4l.c:67:
> /usr/include/linux/time.h:9: redefinition of `struct timespec'
> /usr/include/linux/time.h:88: redefinition of `struct timeval'
>
>
> Any idea which other include references timespec again? Or just what to do
> to get this working?
>
> Thanks
> John
>
> --__--__--
>
> Message: 11
> From: Donald Quaid <dquaid at kittypuss.org>
> To: sane-devel at www.mostang.com
> Date: Thu, 10 Apr 2003 00:23:48 -0500
> Subject: [sane-devel] No devices found with mustek III ep plus
>
> [root at mew ntr]# SANE_DEBUG_MUSTEK_PP=255 scanimage
> [sanei_debug] Setting debug level of mustek_pp to 255.
> [mustek_pp] sane-mustek_pp, version 0.12-alpha. build for SANE 1.0.11
> [mustek_pp] backend by Jochen Eisinger <jochen.eisinger at gmx.net>
> [mustek_pp] sane_init: parse error in line 13: unexpected ``option''
> [mustek_pp] sane_init: parse error in line 20: unexpected ``option''
> [mustek_pp] sane_init: parse error in line 23: unexpected ``option''
> [mustek_pp] sane_init: parse error in line 26: unexpected ``option''
> [mustek_pp] sane_init: parse error in line 29: unexpected ``option''
> [mustek_pp] sane_init: parse error at beginning of line 38
> [mustek_pp] sane_init: parse error at beginning of line 61
> [mustek_pp] sane_init: parse error at beginning of line 62
> [mustek_pp] sane_init: parse error at beginning of line 63
> [mustek_pp] sane_init: parse error in line 64: unexpected ``option''
> [mustek_pp] sane_init: parse error in line 89: unexpected ``option''
> [mustek_pp] sane_init: parse error in line 92: unexpected ``option''
> scanimage: no SANE devices found
> [mustek_pp] sane_exit: all drivers unloaded
> [root at mew ntr]#
>
> /etc/sane.d/dll.conf has
> mustek
> mustek_pp
>
> both Un commented.
>
> sorry if I forgot anything else, I have been
> smashing my keyboard in frustration over this.
>
>
>
> --__--__--
>
> Message: 12
> Date: Thu, 10 Apr 2003 10:08:21 +0200
> From: edg1 at tiscali.be
> Subject: RE: [sane-devel] No devices found with mustek III ep plus
> To: sane-devel at www.mostang.com
>
>
> From: Donald Quaid <dquaid at kittypuss.org>
>
> >To: sane-devel at www.mostang.com
> >Subject: [sane-devel] No devices found with mustek III ep plus
> >Date: Thu, 10 Apr 2003 00:23:48 -0500
> >
> >
> >[root at mew ntr]# SANE_DEBUG_MUSTEK_PP=255 scanimage
> >[sanei_debug] Setting debug level of mustek_pp to 255.
> >[mustek_pp] sane-mustek_pp, version 0.12-alpha. build for SANE 1.0.11
> >[mustek_pp] backend by Jochen Eisinger <jochen.eisinger at gmx.net>
> >[mustek_pp] sane_init: parse error in line 13: unexpected ``option''
> >
> > [...]
> >
> >/etc/sane.d/dll.conf has
> >mustek
> >mustek_pp
> >
> >both Un commented.
> >
> >sorry if I forgot anything else, I have been
> >smashing my keyboard in frustration over this.
>
> The parse errors occur when parsing the mustek_pp.conf file
> (probably also in /etc/sane.d, possibly in /usr/local/etc/sane.d).
>
> The format of the configuration file has changed between 1.0.9 and
> 1.0.10, so maybe you are using an old format. (Or you have a
> mustek_pp.conf file at both locations, and sane is picking up
> the wrong one).
>
> Your mustek_pp.conf file should only contain something
> like this (assuming it's a CCD scanner, not a CIS).
>
> scanner Mustek-III-EP+ 0x378 ccd300
>
> Regards,
>
> Eddy
>
>
> ---------------------------------
> U surft met een klassieke telefoonlijn?
> Bespaar tot 25% met Tiscali Complete !
> Speciaal aanbod : eerste abonnementsjaar gratis.
> ... Meer info op http://complete.tiscali.be
>
>
>
> --__--__--
>
> Message: 13
> Date: Thu, 10 Apr 2003 10:51:34 +0200
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: sane-devel at www.mostang.com
> Subject: Re: [sane-devel] Compile problem in 1.0.11
>
> Hi,
>
> On Thu, Apr 10, 2003 at 12:46:27AM -0300, John Coppens wrote:
> > Get this error on compiling sane-backends 1.0.11:
>
> Please provide more details. This is which Linux version? Which
> version of glibc? Which distribution? Which gcc?
>
> I haven't seen any bug reports about this ever. The include hasn't
> changed since ... well ... since the beginning of the time :-)
>
> > gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include
> > -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d
> > -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0
> > -DBACKEND_NAME=v4l -DLIBDIR=/usr/local/lib/sane v4l.c -fPIC -DPIC -o
> > v4l.lo
> > In file included from /usr/include/linux/videodev2.h:16,
> > from /usr/include/linux/videodev.h:14,
> > from v4l.c:76:
> > /usr/include/linux/time.h:9: redefinition of `struct timespec'
> > /usr/include/linux/time.h:88: redefinition of `struct timeval'
> > /usr/include/linux/time.h:93: redefinition of `struct timezone'
> > /usr/include/linux/time.h:124: redefinition of `struct itimerval'
> >
> > In v4l.c, line 67, I changed:
> >
> > #include <sys/time.h>
> > to
> > #include <linux/time.h>
>
> That doesn't look right. We shouldn't include the low-level headers if
> th at's not absolutely necessary. However, I think we don't need
> sys/time.h anyway. At least for me it compiles without that include.
>
> > which eliminated two errors and left:
> >
> > In file included from v4l.c:67:
> > /usr/include/linux/time.h:9: redefinition of `struct timespec'
> > /usr/include/linux/time.h:88: redefinition of `struct timeval'
> >
> >
> > Any idea which other include references timespec again? Or just what to
> > do to get this working?
>
> Maybe one of the standard system headers includes sys/time.h?
>
> Are you sure that you have the headers that came with glibc in
> /usr/include/linux? Sometimes /usr/include/linux is a link to
> /usr/src/linux/include/linux, that causes all sorts of problems when
> the kernel headers change and is strongly discouraged.
>
> Bye,
> Henning
>
> --__--__--
>
> Message: 14
> Date: Thu, 10 Apr 2003 11:28:27 +0200
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> To: sane-devel at www.mostang.com
> Subject: Re: [sane-devel] Hai, about probe_scanner can't be probed
>
> Hi,
>
> On Tue, Apr 08, 2003 at 10:41:33PM +0800, Fan Dan wrote:
> > Hai, Henning
>
> Have you read my response to your other posting? Could you please
> answer my questions? If something is unclear, please ask. I'm not a
> native English speaker so sometimes I'm writing crap :-)
>
> Ok, I understand the problem now. The scanner has two endpoints with
> the same number but different "directions":
> bEndpointAddress = 81 (in)
> bEndpointAddress = 01 (out)
>
> I have never seens this. In fact I just have checked all the outputs
> of scanners I have and none uses the same number for two different
> endpoints.
>
> Does anyone know if that's complient to the USB spec at all?
>
> > Today, I modified scanner.c for Mustek A3Pro usb scanner (0x055f
> > 0x0401)
> > In probe_scanner.
> > modified
> > have_bulk_in = 1
> > have_bulk_out =2
> > have_intr = 3
> > to
> > have_bulk_in = 0
> > have_bulk_out = 1
> > have_bulk_intr = 2
> >
> >
> > /////////////////////////////////////////
> > + have_bulk_in--
> > + have_bulk_out--
> > + have_intr--
> >
> > then scanner that has three endpoints can be probed successly, because
> > maxpacketout[3] = 0, but maxpacketout[2] = 1 in USB module;
>
> I see. But wouldn't be the right approach:
>
> have_bulk_in = 1
> have_bulk_out = 1
> have_bulk_intr = 2
>
> At least according to your log in your previous message?
>
> > And scanner can be writed, but we can't read from that. so I midified
> > some code int read_scanner function.
> > //////////////////////////////////////////////////////
> > - result = usb_bulk_msg(dev, usb_rcvbulkpipe(dev, scn->bulk_in_ep), ibuf,
> > this_read, &partial, scn->rd_nak_timeout);
> > + result = usb_bulk_msg(dev, usb_rcvbulkpipe(dev, scn->bulk_out_ep),
> > ibuf, this_read, &partial, scn->rd_nak_timeout);
> > /////////////////////////////////////////////////////
> > Then scanner can be write and read.
>
> Ok, but I'll never accept code like this in the kernel :-)
>
> > I want to know that there are three endpoint in scanner, but why both in
> > bulk and out bulk are in same ep? Whether is that OK??
>
> I don't think so, but I'll have to check the USB spec. It's extremely
> unusual at least.
>
> I'll ask on linux-usb-devel for some details.
>
> Bye,
> Henning
>
>
> --__--__--
>
> _______________________________________________
> Sane-devel mailing list
> Sane-devel at www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel
>
>
> End of Sane-devel Digest
More information about the sane-devel
mailing list