[sane-devel] HP Scanjet 2400c for genesys

2006-07-21 Thread Parag N(पराग़)
Hi,
On 7/14/06, St?phane VOLTZ stef...@modulonet.fr wrote:
 Le jeudi 13 juillet 2006 12:17, Parag N() a ?crit:
  Hi Stef,
 
  On 7/12/06, St?phane VOLTZ stef...@modulonet.fr wrote:
   Hello,
   I have started a document at
   http://perso.modulonet.fr/~stefdev/sane/gl646.odt which is in early
   stages, I'll improve it this next days.
 
I have added some contents there. Can you check it?
  Attaching gl646.odt here.
  Regards,
  Parag.

 I'll be off for a few days, will have a look at it next week.

 Are you back from holidays?
Regards,
Parag.
From masn...@gftp.org  Fri Jul 21 21:53:01 2006
From: masn...@gftp.org (Brian Masney)
Date: Fri Jul 21 21:53:08 2006
Subject: [sane-devel] Debug output from Lexmark X1270 scanner
Message-ID: b0e1cc100607211453g1308a254xeccb423fe32bb...@mail.gmail.com

Hi,
   I just bought a Lexmark X1270 printer/scanner. Sane is able to
recognize the scanner using the X1100 driver. Whenever I try to scan
something, the scanner makes a loud noise and the scanning head does
not move. It appears that the head may be trying to go the wrong way.
I am using Sane 1.0.17-3 from the Debian testing distribution. Here is
the debug output from the driver.

[sanei_debug] Setting debug level of lexmark to 20.
[lexmark] SANE Lexmark backend version 1.0-0
[lexmark] sane_init: version_code=0xbff75468
[lexmark] attachLexmark: devname=libusb:002:021
[lexmark] sane_get_devices: device_list=0xbff754b8, local_only=0
[lexmark] sane_open: devicename=libusb:002:021, handle=0xbff77338
[lexmark] sane_open: devname from list: libusb:002:021
[lexmark] init_options: lexmark_device = 0x8246830
[lexmark] sanei_lexmark_x1100_open_device: devnum=0
[lexmark] sane_control_option: handle=0x8246830, opt=0, act=0,
val=0x80db354, info=(nil)
[lexmark] Option value = 6
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_control_option: handle=0x8246830, opt=1, act=0,
val=0x826bc98, info=(nil)
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_control_option: handle=0x8246830, opt=2, act=0,
val=0xbff7734c, info=(nil)
[lexmark] Option value = 150
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 3
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 4
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 4
[lexmark] sane_control_option: handle=0x8246830, opt=4, act=0,
val=0x826bc98, info=(nil)
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 5
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_control_option: handle=0x8246830, opt=1, act=0,
val=0x8284ca8, info=(nil)
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_control_option: handle=0x8246830, opt=2, act=0,
val=0xbff76f04, info=(nil)
[lexmark] Option value = 150
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_get_parameters: handle=0x8246830, params=0x80db470
[lexmark] sane_get_parameters: Data size determined as f7314
[lexmark] sane_get_parameters:
[lexmark]   format: SANE_FRAME_RGB
[lexmark]   last_frame: TRUE
[lexmark]   lines 2ee
[lexmark]   depth 8
[lexmark]   pixels_per_line 1c2
[lexmark]   bytes_per_line 546
[lexmark] sane_get_parameters: handle=0x8246830, params=0x80db470
[lexmark] sane_get_parameters: Data size determined as f7314
[lexmark] sane_get_parameters:
[lexmark]   format: SANE_FRAME_RGB
[lexmark]   last_frame: TRUE
[lexmark]   lines 2ee
[lexmark]   depth 8
[lexmark]   pixels_per_line 1c2
[lexmark]   bytes_per_line 546
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 4
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_control_option: handle=0x8246830, opt=1, act=0,
val=0x827e8b0, info=(nil)
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 2
[lexmark] sane_control_option: handle=0x8246830, opt=2, act=0,
val=0xbff7600c, info=(nil)
[lexmark] Option value = 150
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 3
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 4
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 4
[lexmark] sane_control_option: handle=0x8246830, opt=4, act=0,
val=0x8283a28, info=(nil)
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 5
[lexmark] sane_get_option_descriptor: handle=0x8246830, option = 1
[lexmark] sane_get_option_descriptor: 

[sane-devel] HP Scanjet 2400c for genesys

2006-07-15 Thread Gerald Murray
 
 IIRC, after power up, I just selected mono and started scanning.
 If you want, I can do this again and carefully record the single
 steps.
 
 Bye,
   Uwe

Hi,
For now, I do not it re-done.  I am going to try to get an understanding
of what was done in that log, and why.   From what I have looked into
so far, that program seems to have been less than a straight-forward
design.  I need to try some tests for undocumented register(s) to see if
that changes results.  This may take some time as well, so I do not 
expect results soon.  I am hoping to just use this one log, and then
see if that can get any kind of result.
Thanks for producing that log.

Gerald



[sane-devel] HP Scanjet 2400c for genesys

2006-07-14 Thread Uwe Stange
Hi all,

Gerald Murray wrote:
 I have looked into the log posted on July 5 by Uwe Stange.
 The frontend setup alternates between color and mono three times
 before finally using mono for the scan.
 That it did alternate many times was interesting, I thought.

IIRC, after power up, I just selected mono and started scanning.
If you want, I can do this again and carefully record the single
steps.

Bye,
Uwe




[sane-devel] HP Scanjet 2400c for genesys

2006-07-13 Thread Parag N(पराग़)
Hi Stef,
On 7/12/06, St?phane VOLTZ stef...@modulonet.fr wrote:
 Hello,
 I have started a document at
 http://perso.modulonet.fr/~stefdev/sane/gl646.odt which is in early stages,
 I'll improve it this next days.

  I have added some contents there. Can you check it?
Attaching gl646.odt here.
Regards,
Parag.
-- next part --
A non-text attachment was scrubbed...
Name: gl646.odt
Type: application/octet-stream
Size: 11178 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060713/6e16805a/gl646.obj
From gmur...@cloudnet.com  Thu Jul 13 05:25:32 2006
From: gmur...@cloudnet.com (Gerald Murray)
Date: Thu Jul 13 16:09:57 2006
Subject: [sane-devel] HP Scanjet 2400c for genesys
Message-ID: 1152768332.44b5d94cef...@webmail.cloudnet.com

Hi all,

I have looked into the log posted on July 5 by Uwe Stange.

The frontend setup alternates between color and mono three times
before finally using mono for the scan.

URB 8, 63, and 104 setup color
URB 23, 78 and 119 setup mono

after 119, finally deciding on mono, that log shows
URBs 705 931 2881 3639 3700 4079 re-assert mono.

That it did alternate many times was interesting, I thought.

Best regards,
Gerald





[sane-devel] HP Scanjet 2400c for genesys

2006-07-12 Thread Stéphane VOLTZ
Hello,

I have started a document at 
http://perso.modulonet.fr/~stefdev/sane/gl646.odt which is in early stages, 
I'll improve it this next days.


Regards,
Stef


[sane-devel] HP Scanjet 2400c for genesys

2006-07-06 Thread Parag N(पराग़)
Hi all,
On 7/5/06, Gabriel Guerreiro gabriel.guerre...@gmail.com wrote:
 I have such a log.
 Sending in attachment.

 Sent it to stef last week.
 It's too long to send to the list.

 I could help with some tests too.

 I tried the patch you posted on the list, and made some scans.

 The image is unintelligible and dark.

 I reversed some changes in that patch:
   I don't need to hack the warmup.
   The gamma was being set twice.

 I tried to apply some of the configs of the hp2300, but with no results.
Yes i know that patch is not giving any output. My
observations for this scanner are
1)Warmup code is not passing test so scanner is not moving at all. So
i need to modify warmup code so that scanner will start moving.
2)Also i did similar stuff of configuring HP2400 code like HP2300
wherever it applies but no results.
 Anyway will check log from you all.
Regards,
Parag.


[sane-devel] HP Scanjet 2400c for genesys

2006-07-06 Thread Stéphane VOLTZ
Le mardi 4 juillet 2006 11:51, Thomas Mader a ?crit?:
 Hello,

 I have a HP Scanjet 2400c and would like to know if I can help somehow to
 speed up the development of the driver for this?
 Can I provide some information about it or something else?


Hello,

this topic has come a few time on the list. The way I see 2400 support 
added 
is to record usb activity under windows, decode it. Then modify the genesys 
backend accordingly. Test the changes, and compare debug output until it is 
close enough to windows behaviour.

However, I think there is a 'roadmap': take the functions one after the 
other 
in the sequence they are used by the  backend. For instance, it make no sense 
to directly jump to the final scan and trying to hack it, since it relies on 
values detected by previous functions.

Here's the call graph for a preview:

sane_open
gl646_init
gl646_init_regs
sanei_genesys_create_slope_table
sanei_genesys_create_gamma_table
gl646_set_fe
gl646_slow_back_home
gl646_send_gamma_table
gl646_set_powersaving

sane_start
gl646_save_power
gl646_set_fe

gl646_search_start_position
gl646_setup_sensor
sanei_genesys_exposure_time
gl646_setup_steps
sanei_genesys_create_slope_table
gl646_send_slope_table
gl646_set_fe
gl646_begin_scan
sanei_genesys_read_data_from_scanner
 this function generates a searh_position16.pnm and 
search_position.pnm
which are pictures of the innings of the scanner. These 
should contain
black and white areas that will be basis for postion 
detection.
gl646_end_scan
sanei_genesys_search_reference_point

... more to come ... 

I'm currently compelting this, but I think making 
gl646_search_start_position 
working will take enough time to let me finish.


Some on these functions already test for HP2300. You can add 
tests and 
values for 2400 there. However, there are two points to take into account:
- for the HP2300 I made the analog frontend work like the MD5345 one 
since
I couldn't make it work like it is in usb logs.
-  motor slope creation should favor 
sanei_genesys_create_slope_table3() over
the sanei_genesys_create_slope_table() currently used.

I append the latest version of the scripts that I use for log decoding. 
 The 
cmd.sh takes a decoded log and emits scanner status at each motor start 
(which is used as a 'commit'). It is usefull since you can take it's output 
to compare scanner internal state with the one from the backend log (output 
of gl646_bulk_write_register() ) right before gl646_begin_scan().

Don't hesitate to ask for more or send patches ...

Regards,
Stef



-- next part --
A non-text attachment was scrubbed...
Name: scripts.tar.bz2
Type: application/x-tbz
Size: 15628 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060706/db074ddb/scripts.tar.bin
From ni...@rmk.co.il  Thu Jul  6 06:49:39 2006
From: ni...@rmk.co.il (Nigel Ridley)
Date: Thu Jul  6 06:50:29 2006
Subject: [sane-devel] Only superuser can scan
In-Reply-To: 44a9414c.3050...@wayforth.co.uk
References: 44a9414c.3050...@wayforth.co.uk
Message-ID: 44acb283.8080...@rmk.co.il

Antony Gelberg wrote:
 Hi all,
 
 This is a Debian testing box.  The normal user can't scan, but it's
 different to permissions problems that I've seen before.  He can see a
 scanner, but there is a question mark in the (incomplete) output of
 sane-find-scanner.  It's a Canon lide 60 (genesys backend).  I have
 bodged the permissions on /proc/bus/usb/001/002 to allow all rw, but no
 difference.  It's running 2.6.15, with udev, not hotplug.
 
 aft:/home/dr# sane-find-scanner -q
 found USB scanner (vendor=0x04a9 [Canon], product=0x221c [CanoScan],
 chip=GL841) at libusb:001:002
 aft:/home/dr# su dr
 dr@aft:~$ sane-find-scanner -q
 found USB scanner (vendor=0x04a9, product=0x221c, chip=GL841?) at
 libusb:001:002
 dr@aft:~$ id
 uid=1001(dr) gid=513(Domain Users)
 groups=46(plugdev),110(scanner),111(saned),513(Domain Users)
 dr@aft:~$ ls -l /proc/bus/usb/001/002
 -rw-rw-rw- 1 root root 57 2006-07-02 17:26 /proc/bus/usb/001/002
 dr@aft:~$ scanimage --version
 scanimage (sane-backends) 1.0.17; backend version 1.0.17
 dr@aft:~$ uname -a
 Linux aft 2.6.15-1-k7 #2 Mon Mar 6 15:42:39 UTC 2006 i686 GNU/Linux
 
 Any advice would be appreciated.
 
 Antony
 


-- 
PrayingForIsrael.net
http://www.prayingforisrael.net/

Messianic E-Cards.com
http://www.messianicecards.com/




[sane-devel] HP Scanjet 2400c for genesys

2006-07-06 Thread Parag N(पराग़)
Hi,
On 7/6/06, St?phane VOLTZ stef...@modulonet.fr wrote:
 Le mardi 4 juillet 2006 11:51, Thomas Mader a ?crit:
  Hello,
 
  I have a HP Scanjet 2400c and would like to know if I can help somehow to
  speed up the development of the driver for this?
  Can I provide some information about it or something else?
 

 Hello,

 this topic has come a few time on the list. The way I see 2400 
 support added
 is to record usb activity under windows, decode it. Then modify the genesys
 backend accordingly. Test the changes, and compare debug output until it is
 close enough to windows behaviour.

 However, I think there is a 'roadmap': take the functions one after 
 the other
 in the sequence they are used by the  backend. For instance, it make no sense
 to directly jump to the final scan and trying to hack it, since it relies on
 values detected by previous functions.

 Here's the call graph for a preview:

 sane_open
 gl646_init
 gl646_init_regs
 sanei_genesys_create_slope_table
 sanei_genesys_create_gamma_table
 gl646_set_fe
 gl646_slow_back_home
 gl646_send_gamma_table
 gl646_set_powersaving

 sane_start
 gl646_save_power
 gl646_set_fe

 gl646_search_start_position
 gl646_setup_sensor
 sanei_genesys_exposure_time
 gl646_setup_steps
 sanei_genesys_create_slope_table
 gl646_send_slope_table
 gl646_set_fe
 gl646_begin_scan
 sanei_genesys_read_data_from_scanner
  this function generates a searh_position16.pnm and 
 search_position.pnm
 which are pictures of the innings of the scanner. 
 These should contain
 black and white areas that will be basis for postion 
 detection.
 gl646_end_scan
 sanei_genesys_search_reference_point

 ... more to come ...

 I'm currently compelting this, but I think making 
 gl646_search_start_position
 working will take enough time to let me finish.


 Some on these functions already test for HP2300. You can add 
 tests and
 values for 2400 there. However, there are two points to take into account:
 - for the HP2300 I made the analog frontend work like the MD5345 one 
 since
 I couldn't make it work like it is in usb logs.
 -  motor slope creation should favor 
 sanei_genesys_create_slope_table3() over
 the sanei_genesys_create_slope_table() currently used.

 I append the latest version of the scripts that I use for log 
 decoding.  The
 cmd.sh takes a decoded log and emits scanner status at each motor start
 (which is used as a 'commit'). It is usefull since you can take it's output
 to compare scanner internal state with the one from the backend log (output
 of gl646_bulk_write_register() ) right before gl646_begin_scan().

 Don't hesitate to ask for more or send patches ...

 Regards,
 Stef
 From my side Function call trace for gl646_init(). Its not recursive trace.
===
 gl646_init
sanei_genesys_get_status
gl646_init_regs
   sanei_genesys_create_slope_table
   sanei_genesys_create_gamma_table
   sanei_usb_control_msg
   sanei_genesys_write_register
  gl646_bulk_write_register
  gl646_asic_test
  gl646_set_fe
  gl646_bulk_read_data
  gl646_slow_back_home
  sanei_genesys_init_shading_data
  gl646_repark_head
  gl646_send_gamma_table
  gl646_set_powersaving
=
 I will submit more call trace by tomorrow.
Regards,
Parag.


[sane-devel] HP Scanjet 2400c for genesys

2006-07-05 Thread Parag N(पराग़)
Hi,
On 7/4/06, Thomas Mader thez...@gmail.com wrote:
 Hello,

 I have a HP Scanjet 2400c and would like to know if I can help somehow to
 speed up the development of the driver for this?
 Can I provide some information about it or something else?

   I am also working on this scanner. Can you give me Windows Log for
this scanner. You need to send me USB log of scanner just after its
power up using 
http://benoit.papillault.free.fr/stats/get.php?location=../usbsnoop/sniff-bin-1.8.zip.
Install this zip. start SniffUSB.exe and install sniffer on the
location where you can see Scanner is attached and then powerup
scanner and do take some preview scan of any document under windows.
Then close sniffer application and send me usbsnoop.log file under
windows directory.
Regards,
Parag.


[sane-devel] HP Scanjet 2400c for genesys

2006-07-05 Thread Uwe Stange
Hi,

great, I use this scanner too.

Parag N() wrote:
 Install this zip. start SniffUSB.exe and install sniffer on the
 location where you can see Scanner is attached and then powerup
 scanner and do take some preview scan of any document under windows.
 Then close sniffer application and send me usbsnoop.log file under
 windows directory.

I did as you told. You can find the log file under the following link:

http://www.uwe-stange.de/download/usbsnoop.zip

Tell me if you need more logs.

 Regards,
 Parag.

Bye,
Uwe


[sane-devel] HP Scanjet 2400c for genesys

2006-07-05 Thread Thomas Mader
Hi Parag,

very nice to hear that development is under way. You can get my log from 
http://members.chello.at/ezechiel/usbsnoop.tar.bz2
I hope it's not too much trash in it. If it's unusable or if you need 
something else, just call.

regards,
Thomas

On Wednesday 05 July 2006 15:23, you wrote:
 Hi,

 On 7/4/06, Thomas Mader thez...@gmail.com wrote:
  Hello,
 
  I have a HP Scanjet 2400c and would like to know if I can help somehow to
  speed up the development of the driver for this?
  Can I provide some information about it or something else?

I am also working on this scanner. Can you give me Windows Log for
 this scanner. You need to send me USB log of scanner just after its
 power up using
 http://benoit.papillault.free.fr/stats/get.php?location=../usbsnoop/sniff-b
in-1.8.zip. Install this zip. start SniffUSB.exe and install sniffer on the
 location where you can see Scanner is attached and then powerup
 scanner and do take some preview scan of any document under windows.
 Then close sniffer application and send me usbsnoop.log file under
 windows directory.
 Regards,
 Parag.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060705/83671e49/attachment.pgp
From subscripti...@gnumed.net  Thu Jul  6 00:37:29 2006
From: subscripti...@gnumed.net (Horst Herb)
Date: Thu Jul  6 00:47:03 2006
Subject: [sane-devel] Avision scanner timeout
In-Reply-To: 001701c6a043$78b0bf20$5f00a...@rx30.com
References: 001701c6a043$78b0bf20$5f00a...@rx30.com
Message-ID: 200607061037.29570.subscripti...@gnumed.net

On Thursday 06 July 2006 00:58, Kerry Menzel wrote:
 I am trying to get an Avision AV220 scanner to work with Redhat Linux 9
 (2.4.29-abi). When I connect the scanner the hpusbsci module is

I have that scanner (with USB interface).
It works nicely with the avision module, including Duplex
(but I am using a 2.6.17 kernel on Debian Linux)

Horst