[sane-devel] HP scanjet 2400
Hello list, I have a HP scanjet 2400 scaner and it works well on Debian Squeeze, I get it working with this guide: http://www.elcot.in/linuxdrivers_download.php#Scan2400 This is the info: $ scanimage -L device `genesys:libusb:002:004' is a Hewlett Packard ScanJet 2400c flatbed scanner Is possible to add the drivers on the Debian packages? How can I help with this? Thanks and best regards. -- Josu Lazkano
[sane-devel] Schedule for release of sane-backends 1.0.22
On Thu, 6 Jan 2011, m. allan noah wrote: > Is the generational patch that Gernot discovered in git right now? Yes, it is in. Sorry for the confusion and thanks Nicolas, Gernot & Julien. *t > On Thu, Jan 6, 2011 at 4:19 PM, Nicolas Martin > wrote: >> AFAIK, I've currently only heard about this pending issue for the pixma >> backend, reported by Dustin DeWeese: >> >> https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=312874&group_id=30186 >> >> Maybe Dustin could give us more info about his current test status, >> using the latest git ? >> >> Nicolas >> >> >> Le jeudi 06 janvier 2011 ? 21:03 +0100, Tomas Pospisek a ?crit : >>> On Wed, 5 Jan 2011, Julien BLACHE wrote: >>> "m. allan noah" wrote: I also have a report for the AV120 (#548731). > I've not heard from Nicholas. The pixma fix is still in work, IIRC we should hear back from Gernot in the coming weeks. >>> >>> I think Gernot has confirmed that the one-line fix does fix the machines >>> he has access to. It does also fix my own pixma mp600. We do not know >>> though about generation 1 machines. >>> >>> Aren't we waiting for Nicholas' word on the issue? >>> *t >>> >>> -- >>> sane-devel mailing list: sane-devel at lists.alioth.debian.org >>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel >>> Unsubscribe: Send mail with subject "unsubscribe your_password" >>> ? ? ? ? ? ? ?to sane-devel-request at lists.alioth.debian.org >> >> >> >> -- >> sane-devel mailing list: sane-devel at lists.alioth.debian.org >> http://lists.alioth.debian.org/mailman/listinfo/sane-devel >> Unsubscribe: Send mail with subject "unsubscribe your_password" >> ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org >> > > > > -- > "The truth is an offense, but not a sin" > >
[sane-devel] Schedule for release of sane-backends 1.0.22
AFAIK, I've currently only heard about this pending issue for the pixma backend, reported by Dustin DeWeese: https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=312874&group_id=30186 Maybe Dustin could give us more info about his current test status, using the latest git ? Nicolas Le jeudi 06 janvier 2011 ? 21:03 +0100, Tomas Pospisek a ?crit : > On Wed, 5 Jan 2011, Julien BLACHE wrote: > > > "m. allan noah" wrote: > > > > I also have a report for the AV120 (#548731). > > > >> I've not heard from Nicholas. > > > > The pixma fix is still in work, IIRC we should hear back from Gernot in > > the coming weeks. > > I think Gernot has confirmed that the one-line fix does fix the machines > he has access to. It does also fix my own pixma mp600. We do not know > though about generation 1 machines. > > Aren't we waiting for Nicholas' word on the issue? > *t > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org
[sane-devel] Schedule for release of sane-backends 1.0.22
On Wed, 5 Jan 2011, Julien BLACHE wrote: > "m. allan noah" wrote: > > I also have a report for the AV120 (#548731). > >> I've not heard from Nicholas. > > The pixma fix is still in work, IIRC we should hear back from Gernot in > the coming weeks. I think Gernot has confirmed that the one-line fix does fix the machines he has access to. It does also fix my own pixma mp600. We do not know though about generation 1 machines. Aren't we waiting for Nicholas' word on the issue? *t
[sane-devel] New magicolor backend for inclusion in git
I took a quick look at the code, and only see a few minor issues at first glance. 1. MC_AutoDetectionTimeout is not configurable at runtime 2. the code only calls sanei_usb_init during sane_init. This prevents long-running programs like button press daemons from finding hotplugged scanners. This was discussed recently on the list. 3. Some of your Option Groups could get their names from saneopts.h (SANE_NAME_GEOMETRY, TITLE, DESC, etc) Other than those things, it looks fine to me. allan On Thu, Jan 6, 2011 at 4:39 PM, m. allan noah wrote: > Is the timeout controllable from the config file? > > allan > > On Thu, Jan 6, 2011 at 12:30 PM, Reinhold Kainhofer > wrote: >> As you know, I have been developing a magicolor backend for KONICA MINOLTA >> magicolor 1690MF devices (possibly also for other devices, but I don't have >> access to any other KONICA MINOLTA device that uses the same protocol -- The >> bizhub devices use a different protocol). >> >> In my view, it is now in a state so that it can be included in sane-backends >> (I'm using it regularly with xsane). The git patches can be found at: >> http://www.fam.tuwien.ac.at/~reinhold/sane/magicolor_backend_patches/ >> >> -) The first two (0001 and 0002) are for the sanei_usb functionality already >> send yesterday, >> -) 0003 is the actual backend, >> -) 0004 fixes some compiler warnings in byteorder.h, and >> -) 0005 includes only the changes from running autoreconf (i.e. no manual >> code >> changes!) >> >> >> The backend uses libsnmp (configure check added!) to optionally auto-detect a >> LAN-connected magicolor device. I have set the timeout to a very low value (a >> little more than 1 second!), so all systems without a magicolor scanning in >> the network are not held up by the SNMP auto-detection of the magicolor >> devices. >> On the other hand, if the network is really slow, this might mean that we >> miss >> an SNMP response that takes longer than 1 second! >> >> What do you think of this backend? >> >> Cheers, >> Reinhold >> -- >> -- >> Reinhold Kainhofer, reinhold at kainhofer.com, http://reinhold.kainhofer.com/ >> ?* Financial & Actuarial Math., Vienna Univ. of Technology, Austria >> ?* http://www.fam.tuwien.ac.at/, DVR: 0005886 >> ?* LilyPond, Music typesetting, http://www.lilypond.org >> >> -- >> sane-devel mailing list: sane-devel at lists.alioth.debian.org >> http://lists.alioth.debian.org/mailman/listinfo/sane-devel >> Unsubscribe: Send mail with subject "unsubscribe your_password" >> ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org >> > > > > -- > "The truth is an offense, but not a sin" > -- "The truth is an offense, but not a sin"
[sane-devel] Adding 700F/5600F to the gensys backend
; Hello,
>
>for setting the fe, Wolfson type aren't supported. You'll have to
> copy
> the related part of gl841_set_fe to gl847_set_fe.
>For the d1, d2 registers, this isn't surprising since they are used
> for
> CIS scanners while the 700F is a CCD one. So value doesn't matter.
>For the 6C register, the value just before scan is the more
> important
> since some of its bits drive motor current.
>For the code, the memory layout is indeed driven by capability,
> there is
> a search in a table defined in genesys_gl847.h, please use it. In register
> init, don't replace existing values, but add them with code behind a 'if'.
> For
> instance register 01 should be set like this:
>if(dev->model->is_cis)
> {
>SETREG (0x01, 0x82);
> }
>else
> {
>SETREG (0x01, 0x42);
> }
> look at gl843_init_registers() has other examples on how handling
> different models.
>Also, don't init register A7,A6 they are driven by gpio. Tune gpio
> setting code instead. In init register, don't do SETREG() on registers they
> weren't set before. Other part of the code will take care of them.
>
>I think it would be a good idea to clone the git tree, create your
> own
> branch locally so that you can track your own developments in it and
> eventually send a nice diff.
>
> Regards,
> Stef
>
Hello again,
the 5600F is now giving more sound at startup and the lamp is
even flashing once. The startup writing of data is looking quite
good with some strange artifacts such as trying to write 0x80 to
register 0x05 but getting 0x40 all the time... (see comments in
attached SANE-log). I think discussions on implementation
details have to wait. My focus right now is to get the scanner
responding properly, the implementation can be corrected later.
I am unsuccessful at getting the motor running so far. Any hints
on what to try next would be appreciated.
I am showing you what I have tried so far in the attached file where
one SANE-log and one USB-log is present. There is also a git-diff
for the code so far.
I am currently getting stuck in a loop where the driver is waiting for
data:
[genesys_low] sanei_genesys_read_gl847_register(0x42)=0x00
[genesys_low] sanei_genesys_read_gl847_register(0x43)=0x00
[genesys_low] sanei_genesys_read_gl847_register(0x44)=0x00
[genesys_low] sanei_genesys_read_gl847_register(0x45)=0x00
I am also a bit confused by for example some changing registers:
I have created a CCD-entry for the 5600F-scanner where registers
0x52-0x5e are initialized according to the initial write.
genesys_write_register(0x52,0x0e)
genesys_write_register(0x53,0x00)
genesys_write_register(0x54,0x02)
genesys_write_register(0x55,0x04)
genesys_write_register(0x56,0x06)
genesys_write_register(0x57,0x08)
genesys_write_register(0x58,0x52)
genesys_write_register(0x59,0xe1)
genesys_write_register(0x5a,0x40)
genesys_write_register(0x5e,0x15)
Later in the log when trying to start the scan the following is
happening:
genesys_write_register(0x52,0x02)
genesys_write_register(0x53,0x04)
genesys_write_register(0x54,0x06)
genesys_write_register(0x55,0x08)
genesys_write_register(0x56,0x0a)
genesys_write_register(0x57,0x0c)
genesys_write_register(0x58,0x72)
genesys_write_register(0x59,0x5a)
Which are quite different...
/Stefan
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110106/b1d8551a/attachment-0001.htm>
-- next part --
A non-text attachment was scrubbed...
Name: 5600f_2.tgz
Type: application/x-gzip
Size: 23228 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110106/b1d8551a/attachment-0001.bin>
[sane-devel] New magicolor backend for inclusion in git
As you know, I have been developing a magicolor backend for KONICA MINOLTA magicolor 1690MF devices (possibly also for other devices, but I don't have access to any other KONICA MINOLTA device that uses the same protocol -- The bizhub devices use a different protocol). In my view, it is now in a state so that it can be included in sane-backends (I'm using it regularly with xsane). The git patches can be found at: http://www.fam.tuwien.ac.at/~reinhold/sane/magicolor_backend_patches/ -) The first two (0001 and 0002) are for the sanei_usb functionality already send yesterday, -) 0003 is the actual backend, -) 0004 fixes some compiler warnings in byteorder.h, and -) 0005 includes only the changes from running autoreconf (i.e. no manual code changes!) The backend uses libsnmp (configure check added!) to optionally auto-detect a LAN-connected magicolor device. I have set the timeout to a very low value (a little more than 1 second!), so all systems without a magicolor scanning in the network are not held up by the SNMP auto-detection of the magicolor devices. On the other hand, if the network is really slow, this might mean that we miss an SNMP response that takes longer than 1 second! What do you think of this backend? Cheers, Reinhold -- -- Reinhold Kainhofer, reinhold at kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org
[sane-devel] New magicolor backend for inclusion in git
Is the timeout controllable from the config file? allan On Thu, Jan 6, 2011 at 12:30 PM, Reinhold Kainhofer wrote: > As you know, I have been developing a magicolor backend for KONICA MINOLTA > magicolor 1690MF devices (possibly also for other devices, but I don't have > access to any other KONICA MINOLTA device that uses the same protocol -- The > bizhub devices use a different protocol). > > In my view, it is now in a state so that it can be included in sane-backends > (I'm using it regularly with xsane). The git patches can be found at: > http://www.fam.tuwien.ac.at/~reinhold/sane/magicolor_backend_patches/ > > -) The first two (0001 and 0002) are for the sanei_usb functionality already > send yesterday, > -) 0003 is the actual backend, > -) 0004 fixes some compiler warnings in byteorder.h, and > -) 0005 includes only the changes from running autoreconf (i.e. no manual code > changes!) > > > The backend uses libsnmp (configure check added!) to optionally auto-detect a > LAN-connected magicolor device. I have set the timeout to a very low value (a > little more than 1 second!), so all systems without a magicolor scanning in > the network are not held up by the SNMP auto-detection of the magicolor > devices. > On the other hand, if the network is really slow, this might mean that we miss > an SNMP response that takes longer than 1 second! > > What do you think of this backend? > > Cheers, > Reinhold > -- > -- > Reinhold Kainhofer, reinhold at kainhofer.com, http://reinhold.kainhofer.com/ > ?* Financial & Actuarial Math., Vienna Univ. of Technology, Austria > ?* http://www.fam.tuwien.ac.at/, DVR: 0005886 > ?* LilyPond, Music typesetting, http://www.lilypond.org > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org > -- "The truth is an offense, but not a sin"
[sane-devel] Schedule for release of sane-backends 1.0.22
Is the generational patch that Gernot discovered in git right now? allan On Thu, Jan 6, 2011 at 4:19 PM, Nicolas Martin wrote: > AFAIK, I've currently only heard about this pending issue for the pixma > backend, reported by Dustin DeWeese: > > https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=312874&group_id=30186 > > Maybe Dustin could give us more info about his current test status, > using the latest git ? > > Nicolas > > > Le jeudi 06 janvier 2011 ? 21:03 +0100, Tomas Pospisek a ?crit : >> On Wed, 5 Jan 2011, Julien BLACHE wrote: >> >> > "m. allan noah" wrote: >> > >> > I also have a report for the AV120 (#548731). >> > >> >> I've not heard from Nicholas. >> > >> > The pixma fix is still in work, IIRC we should hear back from Gernot in >> > the coming weeks. >> >> I think Gernot has confirmed that the one-line fix does fix the machines >> he has access to. It does also fix my own pixma mp600. We do not know >> though about generation 1 machines. >> >> Aren't we waiting for Nicholas' word on the issue? >> *t >> >> -- >> sane-devel mailing list: sane-devel at lists.alioth.debian.org >> http://lists.alioth.debian.org/mailman/listinfo/sane-devel >> Unsubscribe: Send mail with subject "unsubscribe your_password" >> ? ? ? ? ? ? ?to sane-devel-request at lists.alioth.debian.org > > > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org > -- "The truth is an offense, but not a sin"
[sane-devel] New magicolor backend for inclusion in git
I can commit on patches 0004 and 0005. * 0004 looks OK to submit at any time. * 0005 - I just updated the files in this area this week based on Fedora 14's version of autofoo tools. Compared to that update, you have a newer version of autoconf then I do but a quite older version of libtool. On top of that, your update overwrote our hand patched ltmain.sh file. If you want to keep it simple, I suggest once you've submitted patch 0003 I can just regenerate all the Makefiles on your behalf. Chris On Thu, Jan 6, 2011 at 11:30 AM, Reinhold Kainhofer wrote: > As you know, I have been developing a magicolor backend for KONICA MINOLTA > magicolor 1690MF devices (possibly also for other devices, but I don't have > access to any other KONICA MINOLTA device that uses the same protocol -- The > bizhub devices use a different protocol). > > In my view, it is now in a state so that it can be included in sane-backends > (I'm using it regularly with xsane). The git patches can be found at: > http://www.fam.tuwien.ac.at/~reinhold/sane/magicolor_backend_patches/ > > -) The first two (0001 and 0002) are for the sanei_usb functionality already > send yesterday, > -) 0003 is the actual backend, > -) 0004 fixes some compiler warnings in byteorder.h, and > -) 0005 includes only the changes from running autoreconf (i.e. no manual code > changes!) > > > The backend uses libsnmp (configure check added!) to optionally auto-detect a > LAN-connected magicolor device. I have set the timeout to a very low value (a > little more than 1 second!), so all systems without a magicolor scanning in > the network are not held up by the SNMP auto-detection of the magicolor > devices. > On the other hand, if the network is really slow, this might mean that we miss > an SNMP response that takes longer than 1 second! > > What do you think of this backend? > > Cheers, > Reinhold > -- > -- > Reinhold Kainhofer, reinhold at kainhofer.com, http://reinhold.kainhofer.com/ > ?* Financial & Actuarial Math., Vienna Univ. of Technology, Austria > ?* http://www.fam.tuwien.ac.at/, DVR: 0005886 > ?* LilyPond, Music typesetting, http://www.lilypond.org > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org >
