[sane-devel] Intend to write driver(s)

2007-06-16 Thread Robert Brijder
Hello,

I have the following two scanners.

* Compeye Simplex 1236C,
  Interface: Parport USB.
  USB id: 0x05cb/0x1483
* Primax Colorado USB 19200,
  Interface: USB,
  USB id: 0x0461/0x0360

The first one is mentioned on the sane website as unsupported, the
second one is not mentioned at all. The output of sane-find-scanner -v
-v with the second scanner connected is show below. My question is,
which scanner would be most easy to write a driver for (I would guess
the first one)? I would then try to write a driver for that one first.

BTW: I have never before written a driver, however I can write in C
and I have read the SANE standard.

Thanks,
Robert


device descriptor of 0x0461/0x0360 at 001:003
bLength   18
bDescriptorType   1
bcdUSB1.00
bDeviceClass  0
bDeviceSubClass   0
bDeviceProtocol   0
bMaxPacketSize0   8
idVendor  0x0461
idProduct 0x0360
bcdDevice 0.00
iManufacturer 2 ((null))
iProduct  7 ((null))
iSerialNumber 0 ()
bNumConfigurations1
 configuration 0
 bLength  9
 bDescriptorType  2
 wTotalLength 32
 bNumInterfaces   1
 bConfigurationValue  1
 iConfiguration   0 ()
 bmAttributes 64 (Self-powered)
 MaxPower 48 mA
  interface 0
   altsetting 0
   bLength9
   bDescriptorType4
   bInterfaceNumber   0
   bAlternateSetting  0
   bNumEndpoints  2
   bInterfaceClass16
   bInterfaceSubClass 1
   bInterfaceProtocol 0
   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

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 (bDeviceClass = 0, bInterfaceClass = 16)
checking for GT-8911 ...
this is not a GT-8911 (check 1, bDeviceClass = 0, bInterfaceClass = 16)
checking for MA-1017 ...
this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 16)
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 (bDeviceClass = 0, bInterfaceClass = 16)
checking for GL646 ...
this is not a GL646 (bcdUSB = 0x100)
checking for GL646_HP ...
this is not a GL646_HP (bDeviceClass = 0, bInterfaceClass = 16)
checking for GL660+GL646 ...
this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 16)
checking for GL841 ...
this is not a GL841 (bDeviceClass = 0, bInterfaceClass = 16)
checking for ICM532B ...
this is not a ICM532B (check 1, bDeviceClass = 0, bInterfaceClass = 16)
checking for PV8630/LM9830 ...
this is not a PV8630/LM9830 (bNumEndpoints = 2)
checking for M011 ...
this is not a M011 (bDeviceClass = 0)
checking for RTS8822L-01H ...
this is not a RTS8822L-01H (bcdUSB = 0x100)
checking for rts8858c ...
this is not a rts8858c (bcdUSB = 0x100)
checking for SQ113 ...
this is not a SQ113 (bcdUSB = 0x100)
Couldn't determine the type of the USB chip (result from sane-backends 1.0.18)

found USB scanner (vendor=0x0461, product=0x0360) at libusb:001:003



[sane-devel] Brother DCP-110c scanner product code

2007-06-16 Thread Johann Botha
Hi!

--8-:- snip -:-8-:- snip -:-8--
root at ra:/etc/udev/rules.d# tail -n4 45-libsane.rules
# Brother DCP-110c
SYSFS{idVendor}==04f9, SYSFS{idProduct}==0169, MODE=664, GROUP=scanner

LABEL=libsane_rules_end
--8-:- snip -:-8-:- snip -:-8--



-- 
RegardsVisit the Frog Shop: http://shop.frogfoot.com/
 Joe

  Simplicate. Add lightness.
-- William B. Stout

 frogfoot networks   +27.21.689.3867   www.frogfoot.com
 visit the swimgeek blog: http://www.swimgeek.com/blog/
-- next part --
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2245 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070616/f1890177/attachment.bin
 


[sane-devel] Intend to write driver(s)

2007-06-16 Thread Étienne Bersac
Hi,

I'm pretty much in the same case. I have two device without driver. I
sent one device to Gerard Jeager who nicely add support for this
device in plustek. I also own another device, but this time, i would
like to add sane support for this device (IRIS IBCR II), but i'm quite
lost in the process. I don't own any Windows(r). Would be nice to
provide a kind of tutorial or any documentation helping new backend
writer.

?tienne.
-- 
verso l'Alto !


[sane-devel] Formulardaten

2007-06-16 Thread cgi-mai...@kundenserver.de


===
== Neuer Eintrag
===

  
---
-- Formular: 'adddev'
---

1. Your email address:
   'alfred.batke at online.de'
2. Manufacturer (e.g. Mustek):
   'Micrtec'
3. Model name (e.g. ScanExpress 1200UB):
   'ScanMaker 4850'
4. Bus type:
   'USB'
5. Vendor id (e.g. 0x001):
   '0x05d9'
6. Product id (e.g. 0x0002):
   '0x30d9'
7. Chipset (e.g. lm9831):
   ''
8. Comments (e.g. similar to Mustek 1234):
   'Both scanners use the same ids. Looks similar to the Microtek ScanMaker 
4800, but the interface classes are different.'
9. Data (e.g. sane-find-scanner -v -v):
   'Output of /proc/bus/usb/devices or sane-find-scanner -v -v

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=05da ProdID=30d9 Rev= 1.00
S:  Product=USB Scanner
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=06(still) Sub=03 Prot=03 Driver=usbscanner
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=83(I) Atr=03(Int.) MxPS=   1 Ivl=3ms
'




[sane-devel] problems compiling dell1600n_net.c on OS/2

2007-06-16 Thread Jon Chambers

Hi Franz,

I just checked in the changes.  Hopefully all should be well now (otherwise 
give me a shout).

The SHUT_RDWR ifdef seems like a good guess but hopefully someone with OS/2 
and this scanner will let me know if it doesn't work.  Actually I've never 
heard of anyone but me using this driver (let alone with OS/2) so this seems 
unlikely but so long as it doesn't break the build :-)

cheers,
Jon

On Thursday 14 June 2007 21:31, Franz Bakan wrote:
  #ifndef SHUT_RDWR
  #define SHUT_RDWR   2
  #endif
 with this workaround the backend compiles. Unfortunately I don't know if it
 works, because I don't have such a device.

-- 
== Jon Chambers =
 http://www.jon.demon.co.uk, 020 8575 7097, 07931 961669
=




[sane-devel] problems compiling dell1600n_net.c on OS/2

2007-06-16 Thread Franz Bakan
On Sat, 16 Jun 2007 19:24:28 +, Jon Chambers wrote:

 I just checked in the changes.  Hopefully all should be well now (otherwise 
 give me a shout).

Thanks, but there are some strange characters ... (codepage  850)

...
/* OS/2... */
#ifndef SHUT_RDWR
#define SHUT_RDWR  ?  ?  ? 2
#endif
...

 The SHUT_RDWR ifdef seems like a good guess but hopefully someone with OS/2 
 and this scanner will let me know if it doesn't work.  Actually I've never 
 heard of anyone but me using this driver (let alone with OS/2) so this seems 
 unlikely but so long as it doesn't break the build :-)

At least it builds here with these modifications (without the strange 
characters)

Bye
Franz





[sane-devel] problems compiling dell1600n_net.c on OS/2

2007-06-16 Thread Jon Chambers

Hi Franz,

On Saturday 16 June 2007 19:41, Franz Bakan wrote:
 Thanks, but there are some strange characters ... (codepage  850)

Now removed (these new-fangled KDE editors are too clever for their own good - 
I should stick to vi!).

 At least it builds here with these modifications (without the strange
 characters)

Good stuff!

cheers,
Jon

-- 
== Jon Chambers =
 http://www.jon.demon.co.uk, 020 8575 7097, 07931 961669
=




[sane-devel] Canon Canoscan 3000ex

2007-06-16 Thread Gerald Murray
REPOST (original lost in transit?)

 How can I start to write a backend?
Hello, welcome!

read:
sane-backends-1.0.18/doc/backend-writing.txt
http://www.xs4all.nl/~ljm/SANE-faq.html

what is known about the scanner  documentation is in
http://www.sane-project.org/unsupported/canon-3000.html

good luck with your effort.

regards,
Gerald