[sane-devel] supported kernels of cvs
Hello all, can someone give an "official" statement about the supported kernel versions for the current cvs. All i found about this is: "CVS is usually only going to work on recent linux kernels" (http://linuxtv.org/v4lwiki/index.php/How_to_build_from_CVS). But what is a recent kernel? Is 2.4.32 a recent one? Background: I'm trying to get a Leadtek WinFast TV2000XP Expert (cx88) running on a 2.4 kernel. Bye Stefan
[sane-devel] usbsnoop2libusb.pl problem
Hello, i decided to have a look what might be needed to get my MD 90070 running with sane. But i'm stuck at the very first steps. according to http://www.meier-geinitz.de/sane/misc/develop.html i followed the link of USB Snoopy which gave me sniffusb-0.13.zip in the end. Also i downloaded usbsnoop2libusb.pl mentioned on Hennings page. After doing some logfile, i started feeding the first logfile to the usbsnoop2libusb.pl (what is the correct command line for this?), but i get lots of errors and no real C code. The error are: - Use of uninitialized value in numeric eq (==) at /home/sle/bin/ usbsnoop2libusb.pl line 58, <> line 42 - Use of uninitialized value in hex at /home/sle/bin/usbsnoop2libusb.pl line 165, <> line 1615 - Use of uninitialized value in hash element at /home/sle/bin/ usbsnoop2libusb.pl line 171, <> line 1615 - Use of uninitialized value in concatenation (.) or string at /home/sle/bin/ usbsnoop2libusb.pl line 173, <> line 1615 - can't find "" i get the first error many times with different line numbers at the end. The incomplete C code looks like, ret = usb_get_descriptor(devh, 0x1, 0x0, buf, 0x012 00120.00466763 ); Without knowing what usb_get_descriptor does, there are at least missing some commas. I have also downloaded SnoopyPro, but its output is in an binary format and i thing this is not the right format for usbsnoop2libusb.pl. So my question is what are the right tools to spy the usb communation and for processing the logfiles? Bye Stefan
[sane-devel] CVS Problem
Hello, i'm unable to login into the cvs server with the information from http://www.sane-project.org/cvs.html : sle@sle3:/usr/src/sane/test$ cvs -d:pserver:anonym...@cvs.alioth.debian.org:/cvsroot/sane login Logging in to :pserver:anonym...@cvs.alioth.debian.org:2401/cvsroot/sane CVS password: cvs [login aborted]: reading from server: Connection reset by peer sle@sle3:/usr/src/sane/test$ Are the information outdated or is anything wron with the cvs? Bye Stefan
[sane-devel] mustek_usb2 & Tevion 90070
Hello, i tried to make the tevion 90070 working with the mustek_usb2 backend. Therefore i patched Prodict and vendor id in mustek_usb2_asic.c . This made scanimage -L working. device `v4l:/dev/video0' is a Noname Leadtek Winfast 2000XP Expert virtual device device `mustek_usb2:libusb:001:002' is a Mustek BearPaw 2448 TA Pro flatbed scanner Note: the name was not patched. Testing scanimage -d mustek_usb2:libusb:001:002 i get an error at dram testing (see attached logfile). Now i'm looking for some hint's how to go on from here. I can do usb logfiles on a win2k box, but how do i "compare" them with the stuff send from the mustek_usb2 backend? Thanks for help Bye Stefan -- next part -- A non-text attachment was scrubbed... Name: sane_ram_test_error.log Type: text/x-log Size: bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070104/59ef2416/sane_ram_test_error.bin From azummo-li...@towertech.it Thu Jan 4 13:01:48 2007 From: azummo-li...@towertech.it (Alessandro Zummo) Date: Thu Jan 4 13:28:42 2007 Subject: [sane-devel] Re: Epson CX11 network scan support? In-Reply-To: <20061226144257.ga19...@apartia.fr> References: <20060522105248.gb28...@apartia.fr> <87hd3habf9@geek.avasys.jp> <20060523083805.ga29...@apartia.fr> <20061218010614.75082311@inspiron> <20061226144257.ga19...@apartia.fr> Message-ID: <20070104130148.01a3dce8@inspiron> On Tue, 26 Dec 2006 15:42:57 +0100 Louis-David Mitterrand wrote: > > Hi David, > > > >you can find a working experimental version in sane cvs. > > Hi Alessandro, > > Thanks for the update. I downloaded the CVS repository and it seems > epson2*.c files need byteorder.h which is not build by default. I tried: > > % autoreconf > configure.in:17: error: possibly undefined macro: AC_NEED_BYTEORDER_H > If this token and others are legitimate, please use > m4_pattern_allow. > See the Autoconf documentation. > autoreconf: /usr/bin/autoconf failed with exit status: 1 > > What should I do to build byteorder.h ? autoreconf regenerates aclocal.m4. please try using autoconf instead, it should work. -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] Medion MD90090 Scanner
Am Sunday 07 January 2007 00:03 schrieb Stefan Pichler: > Dear all, > > i am using ubuntu not very long and got now a Medion MD 90090 Scanner > for present. I saw in the supported hardware list that this scanner is > not supported by sane. My question is now will it be implemented > somewhere in the next releases? > Hello, accoreding to http://www.sane-project.org/lists/sane-mfgs-cvs.html#Z-MEDION-LIFETEC-TEVION-CYTRON and http://www.sane-project.org/unsupported/tevion-md90070.html yor scanner should be the same as my Tevion MD 90070. I currently trying to integrate support for this scanner into the mustek_usb2 backend. This is the good new. The bad new is that i have now ask two time for help on the sane-devel mailing list and i did not any response (maybe this is the reason why the list of unsupported scanners is so long). So the chances are very low to get support for these scanners into the next release of sane. Bye Stefan
[sane-devel] Medion MD90090 Scanner
Am Tuesday 09 January 2007 08:16 schrieb Gerhard Jaeger: > On Monday 08 January 2007 23:35, Stefan Leichter wrote: > > Hello, > > > > accoreding to > > http://www.sane-project.org/lists/sane-mfgs-cvs.html#Z-MEDION-LIFETEC-TEV > >ION-CYTRON and http://www.sane-project.org/unsupported/tevion-md90070.html > > yor scanner should be the same as my Tevion MD 90070. > > > > I currently trying to integrate support for this scanner into the > > mustek_usb2 backend. This is the good new. > > > > The bad new is that i have now ask two time for help on the sane-devel > > mailing list and i did not any response (maybe this is the reason why the > > list of unsupported scanners is so long). > > You have not asked for help, you simply asked for integration - Really? Looks like we have a different understanding of the english language. I allways tried hard to tell you that i will do the modification myself if someone would tell me how to continue from the state where i have been. Looks like iI was not suiccessful so far > that's the difference. If you come back with some specific questions > regarding integration, then I'm pretty sure you'll got some help. > I'm a newbe and i don't get paid for working on OSsoftware. Therefore i like to do the stuff in an efficient way or leave it as it is. I don't like to spend ages. I have no idea if it is enough to switch on some sane logging and compare the output wiith the logs from windows, or is there a need do disassemble the scanner to get a knowledge of the electrical components. Will the programmers manual of the ASIC be enough or are the schematics needed... This are informations i expected to get from some of the experienced members of this list .. > > So the chances are very low to get support for these scanners into the > > next release of sane. > > Depends on you. Partly Stefan
[sane-devel] Tevion MD 90070
Hello, i have a Tevion MD 90070 scanner and like to use in with my Linux box (Debian Etch). Reading sane-project.org i found the best bet is to integrate support for the scanner into the mustek_usb2 backend. if your are willing to get this scanner supported in sane there are two options: 1. Someone gives me a detailed step by step instruction list how to integrate the scanner into the backend or 2. Someone else is doing the implementation and asks me about the required information and for testing. Some infos about me: - i have some knowledge in c programming - a windows 2000 box is close to my linux box, so i can do make usb (1.1) logs if required - i have not done any usb programming Bye Stefan
