[sane-devel] [sane-commit] CVS update of sane-backends (11 files)
Sorry, should have gone to the list: On Feb 18, 2008 4:05 AM, m. allan noah kitno455 at gmail.com wrote: nicolas- please dont remove the lines from canon-mfp.desc, if that external backend still supports those machines. it is ok to have the same machines listed in two different desc files. allan On 2/17/08, Nicolas Martin nicols-guest at alioth.debian.org wrote: Date: Sunday, February 17, 2008 @ 15:49:43 Author: nicols-guest Path: /cvsroot/sane/sane-backends Modified: ChangeLog backend/pixma.c backend/pixma.h backend/pixma_common.c backend/pixma_io_sanei.c backend/pixma_mp150.c backend/pixma_mp730.c backend/pixma_mp750.c doc/descriptions-external/canon_mfp.desc doc/descriptions/pixma.desc doc/sane-pixma.man New models changes: - added: Pixma MP210, MP470, MP520, MP610 - added: MultiPASS MP710 - declared untested: MP140, MP220, MultiPASS MP740 - declared experimental and untested: MP970 Bugs and fixes - multipage documents scan no more fails with non-ADF MPs - IO Fail bug when scanning large pages e.g. with Xsane - implement send_time message form MP710, MP730 family - run indent -gnu on all pixma_* source files. Just to chime in here: Nicolas, the MP710 is a PIXMA device, and the type with extra fax support is the MP740. I am not sure what the untested MultiPASS MP740 is, but you could add the PIXMA MP740 there too I think. Regards, Gernot
[sane-devel] Canon LiDE 90
Guillaume Gastebois schrieb:
Hello,
I try both {0x00, 0x3f, 0x03, 0x26}, and {0x00, 0x3f, 0x00, 0x26},
you can find result under :
http://ggastebois.free.fr/lide90_snoop/17_test1.tar
and http://ggastebois.free.fr/lide90_snoop/17_test2.tar
Looks a lot better. The offset*.pnm actually show a black image,
coarse.pnm is gray. That is good.
I suspect you are still running with the change in thresholds?:
@@ -4545,9 +4546,9 @@
val =
first_line[i * 2 * channels + 2 * j + 1] * 256 +
first_line[i * 2 * channels + 2 * j];
- if (val 10)
+ if (val 1000)
cmin[j]++;
- if (val 65525)
+ if (val 4)
cmax[j]++;
}
Please undo that change. Should give you a nice 2-3-step offset
calibration, that actually works(at least i hope so).
Regarding the output format of the AFE, stay with {0x00, 0x3f, 0x03,
0x26} for now. This does not seem to make any difference, but there are
suspicously many 16 bit words with the binary pattern
.fgh .fgh (that is, the two middle nibbles share the lower 3
bits). We may be sampling the digital image data at the wrong times. As
the most significant byte seems to come through correctly, this does not
need immediate fixing. (On a second thought, this may affect the offset
calibration. See the thesholds. We'll see.)
Regards,
Pierre
[sane-devel] Driver HP scanjet 7800
I am looking for a documentscanner. I saw the HP scanjet 7800. Some internetsites gives the information LINUX driver on request. HP does not have a driver. Is there a 7800 driver in SANE?
[sane-devel] meaning of 1200x2400 etc. explained
On Mon, 18 Feb 2008 12:18:56 +0100 Alessandro Zummo azummo-lists at towertech.it wrote: shall we find a way to tell the driver to enable those new options? maybe a well known sane option ? I'd feel much safer if a frontend can enable it in some explicit way. or with sane_control_option... -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] [sane-commit] CVS update of sane-backends (11 files)
yes- we should make a little effort to keep the external backends files updated. allan On 2/18/08, nicols nicolas.martin at freesurf.fr wrote: Ok, will fix and update the desc and man files today. Can we add then to Canon_mfp .desc file, the latest Canon Pixma models for which Canon has released a driver ? Nicolas Gernot Hassenpflug wrote: Sorry, should have gone to the list: On Feb 18, 2008 4:05 AM, m. allan noah kitno455 at gmail.com wrote: nicolas- please dont remove the lines from canon-mfp.desc, if that external backend still supports those machines. it is ok to have the same machines listed in two different desc files. allan On 2/17/08, Nicolas Martin nicols-guest at alioth.debian.org wrote: Date: Sunday, February 17, 2008 @ 15:49:43 Author: nicols-guest Path: /cvsroot/sane/sane-backends Modified: ChangeLog backend/pixma.c backend/pixma.h backend/pixma_common.c backend/pixma_io_sanei.c backend/pixma_mp150.c backend/pixma_mp730.c backend/pixma_mp750.c doc/descriptions-external/canon_mfp.desc doc/descriptions/pixma.desc doc/sane-pixma.man New models changes: - added: Pixma MP210, MP470, MP520, MP610 - added: MultiPASS MP710 - declared untested: MP140, MP220, MultiPASS MP740 - declared experimental and untested: MP970 Bugs and fixes - multipage documents scan no more fails with non-ADF MPs - IO Fail bug when scanning large pages e.g. with Xsane - implement send_time message form MP710, MP730 family - run indent -gnu on all pixma_* source files. Just to chime in here: Nicolas, the MP710 is a PIXMA device, and the type with extra fax support is the MP740. I am not sure what the untested MultiPASS MP740 is, but you could add the PIXMA MP740 there too I think. Regards, Gernot -- 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 -- View this message in context: http://www.nabble.com/Re%3A--sane-commit--CVS-update-of-sane-backends-%2811-files%29-tp15533287p15540180.html Sent from the SANE - Dev mailing list archive at Nabble.com. -- 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] Problem running as normal user
Hi, i have a problem running as normal user. When i call sane_open it return a null SANE_Handler. this doesn't happen as root (it work fine) Also i can detect the scanner as normal user and scan with scanimage. So i thing it not problem with permissions Any help will be apreciated. Tobias
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'matvancormick at yahoo.com' 2. Manufacturer (e.g. Mustek): 'Plustek' 3. Model name (e.g. ScanExpress 1200UB): 'A8 USB Scanner' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x07b3' 6. Product id (e.g. 0x0002): '0x0448' 7. Chipset (e.g. lm9831): 'gt6816' 8. Comments (e.g. similar to Mustek 1234): 'Saled as Kensington PocketScan (M/N: JSFA8601CU)' 9. Data (e.g. sane-find-scanner -v -v): 'device descriptor of 0x07b3/0x0448 at 003:008 (600dpi USB Scanner) bLength 18 bDescriptorType 1 bcdUSB1.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x07B3 idProduct 0x0448 bcdDevice 5.01 iManufacturer 0 () iProduct 1 (600dpi USB Scanner) iSerialNumber 0 () bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 160 (Remote Wakeup) MaxPower 500 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 '
[sane-devel] Problem running as normal user
SANE_Handle is opaque, you should not try to interpret its value as a pointer. what status code do you get? allan On Feb 18, 2008 8:45 AM, tobias alarcon extobias at gmail.com wrote: Hi, i have a problem running as normal user. When i call sane_open it return a null SANE_Handler. this doesn't happen as root (it work fine) Also i can detect the scanner as normal user and scan with scanimage. So i thing it not problem with permissions Any help will be apreciated. Tobias -- 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] HP ScanJet 5590 issues
On Feb 14, 2008 11:26 PM, Paul C. Bryan email at pbryan.net wrote: ... 1. Overscanning pages (simplex/duplex ADF) If the ADF-scanned page is smaller than the geometry set in the -y parameter value, content from the following page is included on the previous page. It would seem that the backend is not detecting where a page is actually physically stopping, and is simply continuing onto the next page to get the content it wants. Where there is no content (no more pages to feed from the ADF), the remaining expected page area is filled with a quasi-crosshatch pattern). You're right - the scanner doesn't have the paper sensor which could be accessed programmatically (at least original Windows doesn't show such a possibility). Thus pages are distinguished only using image size calculations. However, I havent' seen such a strange behaviour. I'll need to check with one of the scanners I could access. 2. Duplex pages mirrored and upside-down pages (duplex ADF) The backs of pages are being scanned mirrored and upside-down. I have managed to automate a solution to this in a script (attached), which seems to work. The ADF duplex scanning was discovered occasionaly and implemented in most straight way - return double-height pages to scanning application, otherwise an user should mention that he needs 2 x number of pages. 3. Color picture scans are streaked (flatbed) High-contrast areas in the tops of photos seem to streak down below into the rest of scanned photos, causing significant degradation of image quality. This kind of streaking does not seem to occur with lineart scans. Also haven't seen such quality degradation effects, at least our users didn't report such ones. Will also need to check. Could you please open the bug on SANE bug tracker (as mentioned on http://www.sane-project.org/bugs.html) and attach some example pictures which show such effects? Thanks in advance, -- Ilia Sotnikov
[sane-devel] Problem running as normal user
On Feb 18, 2008 11:00 AM, m. allan noah kitno455 at gmail.com wrote: SANE_Handle is opaque, you should not try to interpret its value as a pointer. what status code do you get? i get a SANE_STATUS_IO_ERROR. allan On Feb 18, 2008 8:45 AM, tobias alarcon extobias at gmail.com wrote: Hi, i have a problem running as normal user. When i call sane_open it return a null SANE_Handler. this doesn't happen as root (it work fine) Also i can detect the scanner as normal user and scan with scanimage. So i thing it not problem with permissions Any help will be apreciated. Tobias -- 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] Problem running as normal user
On Feb 18, 2008 9:37 AM, tobias alarcon extobias at gmail.com wrote: On Feb 18, 2008 11:00 AM, m. allan noah kitno455 at gmail.com wrote: SANE_Handle is opaque, you should not try to interpret its value as a pointer. what status code do you get? i get a SANE_STATUS_IO_ERROR. yet if you immediately run scanimage from that same shell it works? which backend is this? allan On Feb 18, 2008 8:45 AM, tobias alarcon extobias at gmail.com wrote: Hi, i have a problem running as normal user. When i call sane_open it return a null SANE_Handler. this doesn't happen as root (it work fine) Also i can detect the scanner as normal user and scan with scanimage. So i thing it not problem with permissions Any help will be apreciated. Tobias -- 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] Canon LiDE 90
Hello,
I made two tests today :
test 1 : too bright/too dard = 10/65525 WITH flag :
SCAN_FLAG_DISABLE_LAMP. Result can bee found on :
http://ggastebois.free.fr/lide90_snoop/18_test1.tar
test 2 : too bright/too dard = 10/65525 WITHOUT flag :
SCAN_FLAG_DISABLE_LAMP. Result can bee found on :
http://ggastebois.free.fr/lide90_snoop/18_test2.tar
Regards
Guillaume
Pierre Willenbrock a ?crit :
Guillaume Gastebois schrieb:
Hello,
I try both {0x00, 0x3f, 0x03, 0x26}, and {0x00, 0x3f, 0x00, 0x26},
you can find result under :
http://ggastebois.free.fr/lide90_snoop/17_test1.tar
and http://ggastebois.free.fr/lide90_snoop/17_test2.tar
Looks a lot better. The offset*.pnm actually show a black image,
coarse.pnm is gray. That is good.
I suspect you are still running with the change in thresholds?:
@@ -4545,9 +4546,9 @@
val =
first_line[i * 2 * channels + 2 * j + 1] * 256 +
first_line[i * 2 * channels + 2 * j];
- if (val 10)
+ if (val 1000)
cmin[j]++;
- if (val 65525)
+ if (val 4)
cmax[j]++;
}
Please undo that change. Should give you a nice 2-3-step offset
calibration, that actually works(at least i hope so).
Regarding the output format of the AFE, stay with {0x00, 0x3f, 0x03,
0x26} for now. This does not seem to make any difference, but there are
suspicously many 16 bit words with the binary pattern
.fgh .fgh (that is, the two middle nibbles share the lower 3
bits). We may be sampling the digital image data at the wrong times. As
the most significant byte seems to come through correctly, this does not
need immediate fixing. (On a second thought, this may affect the offset
calibration. See the thesholds. We'll see.)
Regards,
Pierre
[sane-devel] [sane-commit] CVS update of sane-backends (11 files)
feel free to update the comment in canon_mfp.desc. you can even put in a plug for your free pixma backend. allan On Feb 18, 2008 12:57 PM, nicols nicolas.martin at freesurf.fr wrote: Ok, sounds good to have also an up to date repository of Canon's proprietary scanner backends However, one point about those Canon backends: - Only executable code available, - Work only with Canon's scangearmp software - Seem to be designed for Sane, but AFAIK (self experience on Pixma MP610 and after googling), no one has been able to have them working with Sane (scanimage always fail). IMHO, those external backends are really part of Canon's proprietary code, not sure they can work with current versions of Sane... m. allan noah-3 wrote: yes- we should make a little effort to keep the external backends files updated. allan -- View this message in context: http://www.nabble.com/Re%3A--sane-commit--CVS-update-of-sane-backends-%2811-files%29-tp15533287p15547075.html Sent from the SANE - Dev mailing list archive at Nabble.com. -- 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] meaning of 1200x2400 etc. explained
On Mon, Feb 18, 2008 at 1:35 PM, Oliver Rauch oliver.rauch at rauch-domain.de wrote: Am Freitag, den 15.02.2008, 15:08 +0100 schrieb Alessandro Zummo: On Fri, 15 Feb 2008 07:37:08 -0500 m. allan noah kitno455 at gmail.com wrote: unfortunately, the DPI is not one of the parameters reported to the frontend via sane_get_parameters, so a backend that does not have resolution controls, or one that relies on the scanner to round the resolution will not report the right values. unless that structure gets extended on the bottom :-D Or someone reads the doc and takes a look at the well known options. two places where this does not work: 1. the backend does not expose resolution options because it only has one choice 2. the backend does not know the resolution the scanner will actually use until after the call to start scanning. i have seen machines with both issues. allan -- The truth is an offense, but not a sin
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'sergey at avramov.pp.ru' 2. Manufacturer (e.g. Mustek): 'Mustek' 3. Model name (e.g. ScanExpress 1200UB): 'BearPaw 4800TA Pro II' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x055f' 6. Product id (e.g. 0x0002): '0x040a' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): 'trying libusb: device descriptor of 0x055f/0x040a at 002:037 (Hewlett-Packard. USB2.0 Scanner) bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x055F idProduct 0x040A bcdDevice 1.00 iManufacturer 1 (Hewlett-Packard.) iProduct 2 (USB2.0 Scanner) iSerialNumber 0 () bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 100 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x01 (out 0x01) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 2 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 3 (interrupt) wMaxPacketSize1 bInterval 3 ms bRefresh 0 bSynchAddress 0 trying to find out which USB chip is used checking for GT-6801 ... this is not a GT-6801 (bDeviceClass = 0) checking for GT-6816 ... this is not a GT-6816 (bcdUSB = 0x200) checking for GT-8911 ... this is not a GT-8911 (check 2, bcdUSB = 0x200) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bDeviceClass = 0) checking for MA-1509 ... this is not a MA-1509 (bDeviceClass = 0) checking for LM983[1,2,3] ... this is not a LM983x (bcdUSB = 0x200) checking for GL646 ... this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bDeviceClass = 0, bInterfaceClass = 255) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 255) checking for GL841 ... this is not a GL841 (bDeviceClass = 0, bInterfaceClass = 255) checking for ICM532B ... this is not a ICM532B (check 1, bDeviceClass = 0, bInterfaceClass = 255) checking for PV8630/LM9830 ... this is not a PV8630/LM9830 (bcdUSB = 0x200) checking for M011 ... this is not a M011 (bDeviceClass = 0) checking for RTS8822L-01H ... this is not a RTS8822L-01H (bEndpointAddress = 0x1, bmAttributes = 0x2, wMaxPacketSize = 0x200, bInterval = 0x0) checking for rts8858c ... this is not a rts8858c (bcdUSB = 0x200) checking for SQ113 ... Couldn't set configuration: could not set config 1: Protocol error This USB chip looks like a SQ113? (result from sane-backends 1.0.18) found USB scanner (vendor=0x055f [Hewlett-Packard.], product=0x040a [USB2.0 Scanner], chip=SQ113?) at libusb:002:037 '
[sane-devel] proposal for enabling 1.1 features
An 1.1 compliant frontend should: 1) check for sane version = 1.1 (a macro will be provided) 2) call sane_control_option int supported_version = SOMEMACRO(1,1); sane_control_option(handle, 0, SANE_ACTION_, supported_version, NULL); 3) the backend can then expose sane 1.1 features. I can check every backend driver to see if they can handle a previously unknown SANE_ACTION_XXX and eventually fix them. A frontend that declares itself 1.1 capable should be able to handle unknown frame formats and, generally, be able to correctly use the default: label of any switch statement to handle an unknown condition. Especially when dealing with enums, it is a good practice to not assume that an enum will always have a fixed amount of entries. -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] proposal for enabling 1.1 features
but now a front-end that wants to build against sane1.0 has to define these new macros itself, making portable front-end becomes harder? allan On Mon, Feb 18, 2008 at 2:38 PM, Alessandro Zummo alessandro.zummo at towertech.it wrote: An 1.1 compliant frontend should: 1) check for sane version = 1.1 (a macro will be provided) 2) call sane_control_option int supported_version = SOMEMACRO(1,1); sane_control_option(handle, 0, SANE_ACTION_, supported_version, NULL); 3) the backend can then expose sane 1.1 features. I can check every backend driver to see if they can handle a previously unknown SANE_ACTION_XXX and eventually fix them. A frontend that declares itself 1.1 capable should be able to handle unknown frame formats and, generally, be able to correctly use the default: label of any switch statement to handle an unknown condition. Especially when dealing with enums, it is a good practice to not assume that an enum will always have a fixed amount of entries. -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it -- 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] proposal for enabling 1.1 features
On Mon, 18 Feb 2008 15:00:27 -0500 m. allan noah kitno455 at gmail.com wrote: but now a front-end that wants to build against sane1.0 has to define these new macros itself, making portable front-end becomes harder? why an 1.1 capable frontend should compile against sane 1.0? -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] meaning of 1200x2400 etc. explained
Am Montag, den 18.02.2008, 13:48 -0500 schrieb m. allan noah: two places where this does not work: 1. the backend does not expose resolution options because it only has one choice 2. the backend does not know the resolution the scanner will actually use until after the call to start scanning. i have seen machines with both issues. 1. It is no problem when the scanner only reports one valid resolution in the well known option 2. I have not seen a scanner that does not know the scanning resolution before starting the scan. I think a backend should be able to find out the resolution before starting the scan. If not this may be a little problem, but I do not see a reason for this. Best regards Oliver
[sane-devel] meaning of 1200x2400 etc. explained
On Mon, Feb 18, 2008 at 3:13 PM, Oliver Rauch oliver.rauch at rauch-domain.de wrote: Am Montag, den 18.02.2008, 13:48 -0500 schrieb m. allan noah: two places where this does not work: 1. the backend does not expose resolution options because it only has one choice 2. the backend does not know the resolution the scanner will actually use until after the call to start scanning. i have seen machines with both issues. 1. It is no problem when the scanner only reports one valid resolution in the well known option sure, though it clutters up the scanimage --help output for no reason. 2. I have not seen a scanner that does not know the scanning resolution before starting the scan. I think a backend should be able to find out the resolution before starting the scan. If not this may be a little problem, but I do not see a reason for this. i know, i know, but i am telling you i have a big scanner like this right now. i can hard-code lists of resolutions, and some logic to change to a different list based on the x/y scan area and color/duplex mode, but it sure is easier to hand it off to the scanner when such logic is not documented. allan -- The truth is an offense, but not a sin
[sane-devel] proposal for enabling 1.1 features
On Mon, 18 Feb 2008 15:32:42 -0500 m. allan noah kitno455 at gmail.com wrote: cause it is what is on the user's box. well, it is not absurd for an user to install a recent -dev package if he wants to compile a recent frontend. if a frontend author wants ease the burden of its users, we can just provide a small .h file which contains the two or three macros. -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] [sane-commit] CVS update of sane-backends (11 files)
Updated the pixma external desc file, and renamed MultiPass MP710/MP740 to Pixma MP710/MP740 as suggested in desc and man files. Nicolas Gernot Hassenpflug wrote: Just to chime in here: Nicolas, the MP710 is a PIXMA device, and the type with extra fax support is the MP740. I am not sure what the untested MultiPASS MP740 is, but you could add the PIXMA MP740 there too I think. Regards, Gernot -- View this message in context: http://www.nabble.com/Re%3A--sane-commit--CVS-update-of-sane-backends-%2811-files%29-tp15533287p15549106.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'r.snajdr at coramexport.cz' 2. Manufacturer (e.g. Mustek): 'KONICA MINOLTA' 3. Model name (e.g. ScanExpress 1200UB): 'Bizhub 163' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '132b' 6. Product id (e.g. 0x0002): '204c' 7. Chipset (e.g. lm9831): 'Couldn't determine the type of the USB chip' 8. Comments (e.g. similar to Mustek 1234): 'multifuctional device printer + scaner' 9. Data (e.g. sane-find-scanner -v -v): ' cat /proc/bus/usb/devices T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 11 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=132b ProdID=204c Rev= 1.00 S: Manufacturer=KONICA MINOLTA S: Product=KONICA MINOLTA 163 S: SerialNumber=02112131 C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 1 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms lsusb -vv Bus 001 Device 011: ID 132b:204c Konica Minolta Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x132b Konica Minolta idProduct 0x204c bcdDevice1.00 iManufacturer 1 KONICA MINOLTA iProduct2 KONICA MINOLTA 163 iSerial 3 02112131 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 69 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 2 Bidirectional iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82
[sane-devel] General/Wishlist request
Currently using backend for Canon MP450 - thanks. Need backend for HP 4370 to process 35mm slides. OS is updated Fedora 7. Harv
