[sane-devel] General technical docs for flatbed scanners

Pierre Willenbrock schrieb: > Hi list, > > anybody knows if/where to find $subject on the web? Something that > describes some details of motor control, lamp control and analog/digital > postprocessing, as well as the general scanning operating. Just enough > for a developer of a driver for a dumb

[sane-devel] BRSCAN and BRSCAN2 drivers legal and porting questions

"m. allan noah" wrote: > now, if someone reverse engineers those libraries... I suggest this person goes on with reverse engineering the libes*.so pile of crap needed by the epkowa backend after that. :-) JB. -- Julien BLACHE

[sane-devel] USB device locking in the snapscan backend

Giuseppe Sacco wrote: Hi, > ftok() require a filename, but it does not have to be the pathname of > any scanner device. Since we have an address in the form of > libusb:: I suggest to create > /tmp/libusb:: prior to getting the lock. I am > not sure if this is better than any other file system l

[sane-devel] USB device locking in the snapscan backend

On Sun, 24 Feb 2008 17:12:17 +0100 Julien BLACHE wrote: > Hi, [...] > ftok() returns -1 in this case, but this isn't checked for in this > code, so it happily goes on and semget(0x, 1, ...). [...] ftok() require a filename, but it does not have to be the pathname of any scanner device. S

[sane-devel] USB device locking in the snapscan backend

"m. allan noah" wrote: Hi, > it seems that on linux at least, if the device is left open, no other > process can open it? this achieves the same effect, without any code > at all. That's not exactly the intended use of the mutex... JB. -- Julien BLACHE

[sane-devel] Colors and Calibration of a Genius ColorPage-Vivid 3XE

Hey Allan, Since a some weeks I attempt find Henning because the problem above, without success. You can help-me? Or this is a work for Henning only? I can make more tests and help you (or Henning) to solve the problem, but alone is very difficult. I velieve this is a little bug. Thanks. Rena

[sane-devel] USB device locking in the snapscan backend

Hi, The snapscan backend uses a mutex to lock the USB device it's working with when sending "atomic" commands. We're not talking about pthread mutexes here, which is one of the available implementations, but IPC semaphores. Let's look at the code: static int snapscani_mutex_open(snapscan_mutex_

[sane-devel] Formulardaten

=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'mssa at yahoo.com' 2. Manufacturer (e.g. "Must

[sane-devel] BRSCAN and BRSCAN2 drivers legal and porting questions

On 2/24/08, Predrag Punosevac wrote: > Dear Developers, > > I was wondering if it would be legally possible to include BRSCAN and > BRSCAN2 drivers for Brother all-in-one and scanner devices into the SANE > backhands. > The source code for both drivers is released and I tried to compile on the

[sane-devel] Colors and Calibration of a Genius ColorPage-Vivid 3XE

Hello Henning, I have some problems with my scanner Genius ColorPage-Vivid 3XE and your backend gt68xx. In first time, I accompany the evolution of your backend since years ago, and is a well done work. Congratulations!!! Now, about my problems: The colors is wrong! Seemingly, the problem is i

[sane-devel] BRSCAN and BRSCAN2 drivers legal and porting questions

Dear Developers, I was wondering if it would be legally possible to include BRSCAN and BRSCAN2 drivers for Brother all-in-one and scanner devices into the SANE backhands. The source code for both drivers is released and I tried to compile on the OpenBSD. The compilation fails but it looks to

[sane-devel] USB device locking in the snapscan backend

it seems that on linux at least, if the device is left open, no other process can open it? this achieves the same effect, without any code at all. allan On 2/24/08, Julien BLACHE wrote: > Hi, > > The snapscan backend uses a mutex to lock the USB device it's working > with when sending "atomic"

[sane-devel] Canon CanoScan CS3200F backend

scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080224/b5a5c2f9/attachment.htm

[sane-devel] Canon Pixma MP140 scanner

gt; > > > > > > > > > > Let's do a test ? > > > > > > > > > > > > Could you use please the package file attached, recompile > > > > > > it, and test it again as before (first with the scan utility > > > > > > provided), and send me back the log file produced. > > > > > > > > > > > > Sincerely > > > > > > Nicolas > > > > > > > > > > > > Le samedi 23 f?vrier 2008 ? 07:00 +0700, > > > > > > barbaric.eric at gmail.com a ?crit : > > > > > > > > > > > > > Ok, my notebook is finally fixed, and it still had the old > > > > > > > snooplog I made. Here is a link: > > > > > > > > > > > > > > http://rapidshare.com/files/93990985/USBLogPixmaMP140.zip > > > > > > > > > > > > > > If you need another one, I can make it again. This was > > > > > > > made using Omnipage, and I believe I used 150dpi (the > > > > > > > minimum dpi for that app). > > > > > > > > > > > > > > Eric > > > > > > > -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080224/da0e1594/attachment.htm

[sane-devel] Compile error on latest CVS

Hi again, Il giorno dom, 24/02/2008 alle 09.18 +0100, Giuseppe Sacco ha scritto: > Hi all, > it has been a few months I do compile sane from CVS, but now I am > investigating about this[0] bug, so I started again. [...] It seems I forgot to provide a link to the bug: http://bugs.debian.org/cgi-bi

[sane-devel] Compile error on latest CVS

Hi all, it has been a few months I do compile sane from CVS, but now I am investigating about this[0] bug, so I started again. When I configure and make I use these commands: $ ./configure --prefix=/usr/local BACKENDS=snapscan $ make but the process stop this way: [...] epkowa.desc: Warning: Ba

[sane-devel] Formulardaten

=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: '' 2. Manufacturer (e.g. "Mustek"): '' 3. Mo

[sane-devel] Canon LiDE 90

Hello, I modified these registers. But the scanner locks writting continiously : "[genesys] sanei_genesys_read_register (0x41, 0xf4) completed". I modified 0x1a=0x24 and 0x1d=0x02 in Genesys_Sensor. In log I see 0x1d=0x02 but 0x1a=0x00 ?? I will be long for next answer as I take one week holida