On 01/11/2014 22:15, Myroslav Kavatsyuk wrote:
#define BACKEND_NAME genesys
Hello,
this is because of this define, which should only used by the
backend. Try somezthing like
#define BACKEND_NAME genesys_test
Regards,
Stef
--
sane-devel mailing list: sane-devel@lists.alioth.debi
Dear Stef,
Linking with the libganesys helped a lot (before I was trying to link with
libsane-genesys). However, I still have one linking problem. The linker
reportsthat I have multiple definitions of the same function
sanei_debug_genesys:
./compile/backend/.libs/libgenesys.a(libgenesys_la-genes
On 31/10/2014 22:02, Myroslav Kavatsyuk wrote:
Dear Stef,
The SANE was configured with the proper CFLAGS shell variables:
export CFLAGS="-DUNIT_TESTING=1"
export LDFLAGS="-DUNIT_TESTING=1"
export CPPFLAGS="-DUNIT_TESTING=1"
export BACKENDS=genesys
export PRELOADABLE_BACKENDS=genesys
./configur
Dear Stef,
The SANE was configured with the proper CFLAGS shell variables:
export CFLAGS="-DUNIT_TESTING=1"
export LDFLAGS="-DUNIT_TESTING=1"
export CPPFLAGS="-DUNIT_TESTING=1"
export BACKENDS=genesys
export PRELOADABLE_BACKENDS=genesys
./configure --prefix=/home/xxx/4_pwork/SANE/local/
I have ch
On 29/10/2014 12:18, Myroslav Kavatsyuk wrote:
Dear Stef,
Thanks a lot for a provided example. From your code I have made a
program (see attachment) which
compiles. However, I can not link it with the libsane-genesys.
apparently I miss something.
I have compiled SANE libraries as following:
Dear Stef,
Thanks a lot for a provided example. From your code I have made a program (see
attachment) whichcompiles. However, I can not link it with the libsane-genesys.
apparently I miss something.
I have compiled SANE libraries as following:> export BACKENDS=genesys> export
CFLAGS="-D UNIT_TES
On 30/09/2014 12:05, Myroslav Kavatsyuk wrote:
Dear Stef,
After a summer brake I got again some time to work on the driver for
canoscan 8400F. In order to simplify my task I have disconnected
transparency
unit while taking logs. This made logs more clear. Here are my findings:
1) Sensor prof
Dear Stef,
After a summer brake I got again some time to work on the driver for canoscan
8400F. In order to simplify my task I have disconnected transparency
unit while taking logs. This made logs more clear. Here are my findings:
1) Sensor profiles: For all scan modes only two different sensor
Dear Stef,
After digging into the logs I found that for each scan there are few motor
tables written to the chipset. As example, for 300 dpi scan
I have identified 5 different tables. There are two types of tables: long (2050
32 bit words) and short (256 32 bit words). In attachment
you will fin
On 23/06/2014 15:51, Myroslav Kavatsyuk wrote:
Dear Stef,
Thanks a lot for your suggestions. I have studied genesys
documentation, and indeed it is helpful :)
I have collected usblogs for all useful scan modes. In case you would
like to look at them, you can
download processed (with your scr
Dear Stef,
Thanks a lot for your suggestions. I have studied genesys documentation, and
indeed it is helpful :)
I have collected usblogs for all useful scan modes. In case you would like to
look at them, you can
download processed (with your script) logs at: CS8400F
CS8400F
Shared with Dro
On 04/06/2014 12:22, Myroslav Kavatsyuk wrote:
Dear Stef,
thanks a lot for your suggestions and scripts. The more I dig into the
source code, the more
questions I have. Here they are:
1) file genesys_devices.c, definition of Genesys_Model
canon_8400f_model (line 1691). I realized that the
Dear Stef,
thanks a lot for your suggestions and scripts. The more I dig into the source
code, the more
questions I have. Here they are:
1) file genesys_devices.c, definition of Genesys_Model canon_8400f_model (line
1691). I realized that the dpi list does not correspond to the model (CS8400F
On 01/06/2014 14:19, Myroslav Kavatsyuk wrote:
Dear Stef,
Finally I managed to test the CS8400F. In the git version of SANE there is
some implementation of the scanner. After adding proper line to
genesys.conf
I managed to make first scan with the CS8400F. Scanning was invoked using
scanimage.
Dear Stef,
Finally I managed to test the CS8400F. In the git version of SANE there is
some implementation of the scanner. After adding proper line to genesys.conf
I managed to make
first scan with the CS8400F. Scanning was invoked using
scanimage. Here are my observations:
* If I do not specify s
Hi Brian,
> It was considerably more than a $150 scanner when it came out and supports
> medium format negatives and can scan at a physical 18MP resolution
> (3200x6400) at 48 bit color. I don't know many scanners capable of that.
> Even today. It may not be quite as high end as some dedicated pho
On Fri, October 2, 2009 11:43 am, m. allan noah wrote:
> On Fri, Oct 2, 2009 at 11:53 AM, wrote:
>> I'm back at considering working on a driver for the Canoscan 8400f. I
>> have
>> been requested by another developer to help do this. I have the Mac
>> driver. Mac, if I remember it is *nix based n
On Fri, Oct 2, 2009 at 11:53 AM, wrote:
> I'm back at considering working on a driver for the Canoscan 8400f. I have
> been requested by another developer to help do this. I have the Mac
> driver. Mac, if I remember it is *nix based now. What is the take on
> driver writing in regards to RE drive
I'm back at considering working on a driver for the Canoscan 8400f. I have
been requested by another developer to help do this. I have the Mac
driver. Mac, if I remember it is *nix based now. What is the take on
driver writing in regards to RE drivers to implement drivers? Has anyone
ever decompile
19 matches
Mail list logo
