[sane-devel] Error in HP LaserJet M1005 Backend
Hello I checked hpljm1005.c with your patched 'sane_open' - thich work correct. Wait the AUTHOR's approval? Regards, tropos -- View this message in context: http://www.nabble.com/Error-in-HP-LaserJet-M1005-Backend-tp15127315p15182770.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'criggsaz at cox.net' 2. Manufacturer (e.g. Mustek): 'Hewlett-Packard' 3. Model name (e.g. ScanExpress 1200UB): 'Scanjet 4470c' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x03f0' 6. Product id (e.g. 0x0002): '0x0805' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): '=[ cat /proc/bus/usb/devices ]=== T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0805 Rev= 1.00 S: Manufacturer=Hewlett-Packard S: Product=HP ScanJet 4470c S: SerialNumber=CN24HBC0Z3Z C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=00(ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms =[ sane-find-scanner -v -v ]=== This is sane-find-scanner from sane-backends 1.0.18 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid
[sane-devel] HP Scanjet 7800
Hi, i have HP Scanjet 7800 scanner and this scanner is not supported by sane. I tested avision and hp5590 backend from cvs without success. Which backend support this scanner ? For more information and testing, contact me. Many thanks Pavel Kysilka lsusb -v -d 03f0:2905 Bus 002 Device 004: ID 03f0:2905 Hewlett-Packard Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x03f0 Hewlett-Packard idProduct 0x2905 bcdDevice1.00 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0xc0 Self Powered MaxPower4mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 16
[sane-devel] Error in HP LaserJet M1005 Backend
no, the author seems a little slow to respond, so i have committed this fix now. allan On 1/30/08, tropos tropos at rambler.ru wrote: Hello I checked hpljm1005.c with your patched 'sane_open' - thich work correct. Wait the AUTHOR's approval? Regards, tropos -- View this message in context: http://www.nabble.com/Error-in-HP-LaserJet-M1005-Backend-tp15127315p15182770.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] Formulardaten
Le Sunday 27 January 2008 12:04:42 cgi-mailer at kundenserver.de, vous avez ?crit?: === == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'alistair at penguinmail.com' 2. Manufacturer (e.g. Mustek): 'Hewlett Packard' 3. Model name (e.g. ScanExpress 1200UB): 'scanjet 4470c' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): ' Vendor=03f0 ' 6. Product id (e.g. 0x0002): 'ProdID=0805 Rev= 1.00' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): 'xsane will recognise scanner and seem to perform preview scan, normal scan and so on, but the output is just a black page. I am using Ubuntu Gutsy Gibbon updated to today's version (27.01.2008). Xsane is version 0.991. When I try and set configurations in xsane I get permission denied types of messages. This happens actually even when I just close xsane.' 9. Data (e.g. sane-find-scanner -v -v): '$ scanimage -L device `hp_rts88xx:libusb:002:004' is a Hewlett-Packard ScanJet 4470C flatbed scanner $cat /proc/bus/usb/devices T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 8 B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.06 S: Manufacturer=Linux 2.6.22-14-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1d.7 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0d7d ProdID=1600 Rev= 1.00 S: Manufacturer=Acer S: Product=Flash Disk S: SerialNumber=48541D000264 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=200mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 64 Ivl=1ms T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.06 S: Manufacturer=Linux 2.6.22-14-generic uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.3 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.06 S: Manufacturer=Linux 2.6.22-14-generic uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.2 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.06 S: Manufacturer=Linux 2.6.22-14-generic uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.1 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0805 Rev= 1.00 S: Manufacturer=Hewlett-Packard S: Product=HP ScanJet 4470c S: SerialNumber=CN24GAD059Z C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=00(ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=043d ProdID=0078 Rev= 1.00 S: Manufacturer=Lexmark S: Product=Lexmark Z600 Series S: SerialNumber=18K670127073950 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 4mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp E: Ad=05(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=81(I) Atr=02(Bulk) MxPS= 16 Ivl=0ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor= ProdID= Rev= 2.06 S: Manufacturer=Linux 2.6.22-14-generic uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=:00:1d.0 C:* #Ifs= 1
[sane-devel] Formulardaten
Le Wednesday 30 January 2008 16:37:31 cgi-mailer at kundenserver.de, vous avez ?crit?: === == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'criggsaz at cox.net' 2. Manufacturer (e.g. Mustek): 'Hewlett-Packard' 3. Model name (e.g. ScanExpress 1200UB): 'Scanjet 4470c' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x03f0' 6. Product id (e.g. 0x0002): '0x0805' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): '=[ cat /proc/bus/usb/devices ]=== T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0805 Rev= 1.00 S: Manufacturer=Hewlett-Packard S: Product=HP ScanJet 4470c S: SerialNumber=CN24HBC0Z3Z C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=00(ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms =[ sane-find-scanner -v -v ]=== This is sane-find-scanner from sane-backends 1.0.18 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument)
[sane-devel] Canon LiDE 600F vs. Canon LiDE 70
As reported from sane project Canon LiDE 70 has the same chip (Philips CP2155BE) as Canon LiDE 600F inside. It was supposed that they will behave mostly the same. Now I got reports from users with Canon LiDE 70 and my perl scripts for Canon LiDE 600F to extract image data worked with Canon LiDE 70 as well. So my sane backend to be written has a good chance to support them both. -- Ciao J?rgen Microsoft is not the answer. Microsoft is the question. NO is the answer.
[sane-devel] Canon LiDE 90
But you can ignore led-calibration for now, that is not essential when debugging the backend. Just make sure the exposure settings in Genesys_Sensor.regs_0x10_0x1d are good, for example from an usb log the last register write to 0x10-0x15 before receiving actual scanned data. If those stay all zero, the rgb-leds in your scanner are very probably not controlled using the rgb-led-control-feature of the gl84x. You can disable led calibration by commenting out the code in genesys_flatbed_calibration. Offset/Gain calibration can be commented out when the values in Genesys_Frontend are good, Shading calibration can be disabled when you add OPTICAL_FLAG_DISABLE_SHADING to the flags for gl841_init_optical_regs_scan. When shading calibration is disabled, you get vertical stripes, the others lead to too dark/bright r/g/b channels. Things that may be missing: * leds need to be controlled correctly * cis-sensor needs to get the correct clock signals(line toggle+pixel clock, half-resolution signal is optional for now) * the analog frontend registers need to be setup correctly in Genesys_Frontend * the readout position in the data stream from the analog frontend may need tweaking(registers 0x52,0x53) When that is done, you should be able to get an image from your scanner, although calibration may be lacking. Regards, Pierre OK, i see some image (very far to end result...). But can you explain to me how to know the correct values for genesys_frontend These parameter have big influence on resulting image. Thank you. Guillaume
[sane-devel] Canon LiDE 90
Guillaume Gastebois schrieb: But you can ignore led-calibration for now, that is not essential when debugging the backend. Just make sure the exposure settings in Genesys_Sensor.regs_0x10_0x1d are good, for example from an usb log the last register write to 0x10-0x15 before receiving actual scanned data. If those stay all zero, the rgb-leds in your scanner are very probably not controlled using the rgb-led-control-feature of the gl84x. You can disable led calibration by commenting out the code in genesys_flatbed_calibration. Offset/Gain calibration can be commented out when the values in Genesys_Frontend are good, Shading calibration can be disabled when you add OPTICAL_FLAG_DISABLE_SHADING to the flags for gl841_init_optical_regs_scan. When shading calibration is disabled, you get vertical stripes, the others lead to too dark/bright r/g/b channels. Things that may be missing: * leds need to be controlled correctly * cis-sensor needs to get the correct clock signals(line toggle+pixel clock, half-resolution signal is optional for now) * the analog frontend registers need to be setup correctly in Genesys_Frontend * the readout position in the data stream from the analog frontend may need tweaking(registers 0x52,0x53) When that is done, you should be able to get an image from your scanner, although calibration may be lacking. Regards, Pierre OK, i see some image (very far to end result...). But can you explain to me how to know the correct values for genesys_frontend These parameter have big influence on resulting image. genesys_frontend contains the settings for the analog frontend. the canon lide 35/40/50 seem to be all using the wm8199(afair) or a compatible chip, so that datasheet may be helpful. Datasheets for the wolfson analog frontends can be found on their website: http://www.wolfsonmicro.com/productListings/imaging_sensor_adcs/ gl841_set_fe and the calibration functions are currently setup to handle a wm8199. The reg, reg2 and sign entries need to be obtained from an usb log. I don't know the actual register mapping, but it should be easy to figure that out from gl841_set_fe. gain and offset will be calibrated by one of the calibration functions. The values depend heavily on the LED and Sensor characteristics. For now, when the LED exposure time is constant, you can get away with constant values. There seems to be no way to find the exact analog frontend chip without looking at the pcb, but that is hopefully not needed. Simplified, you get the result of this equation from the analog frontend(The datasheet has the details): v: proportional to input voltage from sensor o: offset(not necessarily the value from the register) g: gain-factor(not necessarily the value from the register) d: digital output value d = (o + v) * g The behaviour of the sensor can be described by this equation: i: proportional to the light intensity, which is proportional to led exposure time and shade on your original v_o: offset voltage s: sensitivity of sensor(voltage per intensity) v = v_o + i * s The offset/gain calibration optimizes offset and gain such that maximum and minimum v fall in the range between maximum and minimum d, but trying to maximize the range used in d(this requires at least one led exposure time to be setup reasonably). The LED calibration tries to get all LED colors to result in a similar value into the analog frontend, by adjusting the exposure time(this requires analog frontend offset/gain values to be setup reasonably). Sorry for the lengthy mail, but i hope the information is helpful. Regards, Pierre
[sane-devel] Error in HP LaserJet M1005 Backend
Le mercredi 30 janvier 2008, m. allan noah a ?crit?: no, the author seems a little slow to respond, so i have committed this fix now. Sorry about that, I'm quite busy thoses times (End of my master project, getting a new job etc ...). Thank you for the fix, it of course has my approval. Regards, Philippe
