[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Primax 9600 usb and linux usb scanner module
From: Bryn Jeffries ####@####.#### Date: 28 Apr 2000 14:33:52 -0000 Message-Id: <20000428152425.A22365@thelonious.new.ox.ac.uk> In trying out my USB scanner I contacted the guy responsible for the usb scanner code. Included is the discussion. I was wondering whether anyone knew how to tackle the problem he states. - i.e can the second IN endpoint be ignored? B. ----- Forwarded message from "David E. Nelson" ####@####.#### ----- Date: Fri, 28 Apr 2000 08:55:15 -0500 (CDT) From: "David E. Nelson" ####@####.#### To: Bryn Jeffries ####@####.#### cc: ####@####.#### Subject: Re: Primax 9600 USB and kernel boot messages Hi Bryn, Thanks for including the messages file. The problems lies the fact that scanner.c only operate in two modes: (1) two bulk endpoints (for for IN and one for OUT) or (2) the same as (1) but with an interrupt endpoint. The Primax has three bulk endpoints (two IN's and one OUT). I don't know if the additional IN endpoint is important or not much less why it is there. If it can be determined that the extra IN is not required then the code could be written to silently ignore it. Since I don't work at the scanner level (only the driver level), others must investigate the actual scanner peculiarities. Regards, /\/elson On Fri, 28 Apr 2000, Bryn Jeffries wrote: > > Dear David, > > I have been trying to get my Primax 9600 USB scanner working under > linux. There has recently been a driver developed for the IBM Ideascan > 2000 (http://ideascan.sourceforge.net ) which I suspect may be very > similar to the Primax 9600. (If you're interested there is a > discussion at http://schwarz.thueday.de/%7Eprimax/ regarding Primax > scanners). > > I'd like to try the code out, but I'm having problems getting things > started - I'm not sure whether the problem lies in my understanding or > in the existing usb scanner code. At the moment I get the following > reports in /var/log/messages: > > ------------------------------------------------- > Apr 28 09:51:55 dhcp-2-161 kernel: usb.c: registered new driver usbdevfs > Apr 28 09:51:55 dhcp-2-161 kernel: usb.c: registered new driver hub > Apr 28 09:51:55 dhcp-2-161 kernel: usb-uhci.c: $Revision: 1.228 $ time 19:26:39 > Apr 27 2000 > Apr 28 09:51:55 dhcp-2-161 kernel: usb-uhci.c: High bandwidth mode enabled > Apr 28 09:51:55 dhcp-2-161 kernel: usb-uhci.c: Intel USB controller: setting lat > ency timer to 0 > Apr 28 09:51:55 dhcp-2-161 kernel: usb-uhci.c: USB UHCI at I/O 0xe000, IRQ 11 > Apr 28 09:51:55 dhcp-2-161 kernel: usb-uhci.c: Detected 2 ports > Apr 28 09:51:55 dhcp-2-161 kernel: usb.c: new USB bus registered, assigned bus n > umber 1 > Apr 28 09:51:55 dhcp-2-161 kernel: usb.c: USB new device connect, assigned devic > e number 1 > Apr 28 09:51:55 dhcp-2-161 kernel: Product: USB UHCI Root Hub > Apr 28 09:51:55 dhcp-2-161 kernel: SerialNumber: e000 > Apr 28 09:51:55 dhcp-2-161 kernel: hub.c: USB hub found > Apr 28 09:51:55 dhcp-2-161 kernel: hub.c: 2 ports detected > > Apr 28 09:51:55 dhcp-2-161 kernel: usb.c: registered new driver usbscanner > Apr 28 09:51:55 dhcp-2-161 kernel: scanner.c: USB Scanner support registered. > > Apr 28 09:51:55 dhcp-2-161 kernel: usb.c: USB new device connect, assigned devic > e number 2 > Apr 28 09:51:55 dhcp-2-161 kernel: Manufacturer: PRIMAX > Apr 28 09:51:55 dhcp-2-161 kernel: Product: Colorado USB 9600 > Apr 28 09:51:55 dhcp-2-161 kernel: scanner.c: probe_scanner: Undetected endpoint > . Notify the maintainer. > Apr 28 09:51:55 dhcp-2-161 kernel: usb.c: This device is not recognized by any i > nstalled USB driver. > Apr 28 09:51:55 dhcp-2-161 kernel: Length = 18 > Apr 28 09:51:55 dhcp-2-161 kernel: DescriptorType = 01 > Apr 28 09:51:55 dhcp-2-161 kernel: USB version = 1.00 > Apr 28 09:51:55 dhcp-2-161 kernel: Vendor:Product = 0461:0340 > Apr 28 09:51:55 dhcp-2-161 kernel: MaxPacketSize0 = 64 > Apr 28 09:51:55 dhcp-2-161 kernel: NumConfigurations = 1 > Apr 28 09:51:55 dhcp-2-161 kernel: Device version = 1.02 > Apr 28 09:51:55 dhcp-2-161 kernel: Device Class:SubClass:Protocol = ff:00:ff > Apr 28 09:51:55 dhcp-2-161 kernel: Vendor class > Apr 28 09:51:55 dhcp-2-161 kernel: Configuration: > Apr 28 09:51:55 dhcp-2-161 kernel: bLength = 9 > Apr 28 09:51:55 dhcp-2-161 kernel: bDescriptorType = 02 > Apr 28 09:51:55 dhcp-2-161 kernel: wTotalLength = 0027 > Apr 28 09:51:55 dhcp-2-161 kernel: bNumInterfaces = 01 > Apr 28 09:51:55 dhcp-2-161 kernel: bConfigurationValue = 01 > Apr 28 09:51:55 dhcp-2-161 kernel: iConfiguration = 03 > Apr 28 09:51:55 dhcp-2-161 kernel: bmAttributes = 40 > Apr 28 09:51:55 dhcp-2-161 kernel: MaxPower = 100mA > Apr 28 09:51:55 dhcp-2-161 kernel: > Apr 28 09:51:55 dhcp-2-161 kernel: Interface: 0 > Apr 28 09:51:55 dhcp-2-161 kernel: Alternate Setting: 0 > Apr 28 09:51:55 dhcp-2-161 kernel: bLength = 9 > Apr 28 09:51:55 dhcp-2-161 kernel: bDescriptorType = 04 > Apr 28 09:51:55 dhcp-2-161 kernel: bInterfaceNumber = 00 > Apr 28 09:51:55 dhcp-2-161 kernel: bAlternateSetting = 00 > Apr 28 09:51:55 dhcp-2-161 kernel: bNumEndpoints = 03 > Apr 28 09:51:55 dhcp-2-161 kernel: bInterface Class:SubClass:Protocol = ff > :00:ff > Apr 28 09:51:55 dhcp-2-161 kernel: iInterface = 00 > Apr 28 09:51:55 dhcp-2-161 kernel: Endpoint: > Apr 28 09:51:55 dhcp-2-161 kernel: bLength = 7 > Apr 28 09:51:55 dhcp-2-161 kernel: bDescriptorType = 05 > Apr 28 09:51:55 dhcp-2-161 kernel: bEndpointAddress = 01 (out) > Apr 28 09:51:55 dhcp-2-161 kernel: bmAttributes = 02 (Bulk) > Apr 28 09:51:55 dhcp-2-161 kernel: wMaxPacketSize = 0040 > Apr 28 09:51:55 dhcp-2-161 kernel: bInterval = 00 > Apr 28 09:51:55 dhcp-2-161 kernel: Endpoint: > Apr 28 09:51:55 dhcp-2-161 kernel: bLength = 7 > Apr 28 09:51:55 dhcp-2-161 kernel: bDescriptorType = 05 > Apr 28 09:51:55 dhcp-2-161 kernel: bEndpointAddress = 82 (in) > Apr 28 09:51:55 dhcp-2-161 kernel: bmAttributes = 02 (Bulk) > Apr 28 09:51:55 dhcp-2-161 kernel: wMaxPacketSize = 0001 > Apr 28 09:51:55 dhcp-2-161 kernel: bInterval = 00 > Apr 28 09:51:55 dhcp-2-161 kernel: Endpoint: > Apr 28 09:51:55 dhcp-2-161 kernel: bLength = 7 > Apr 28 09:51:55 dhcp-2-161 kernel: bDescriptorType = 05 > Apr 28 09:51:55 dhcp-2-161 kernel: bEndpointAddress = 83 (in) > Apr 28 09:51:55 dhcp-2-161 kernel: bmAttributes = 02 (Bulk) > Apr 28 09:51:55 dhcp-2-161 kernel: wMaxPacketSize = 0040 > Apr 28 09:51:55 dhcp-2-161 kernel: bInterval = 00 > > ------------------------------------------------------- > > In particular there is an "undetected endpoint, notify maintainer" > message, which is why I felt I should contact you. Do you think you > could possibly point me in a useful direction? I'm running redhat 6.2, > with kernel 2.3.99-pre5, and I created the suggested /dev/usbscanner > and /dev/usbscanner0 files as instructed in the text files. > Any help would be much appreciated. > > Many thanks, > > Bryn Jeffries > > > > > > > -- ~~ ** ~~ Help the recycle effort by recycling e-mail. ~~ ** ~~ ----- End forwarded message ----- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Primax 9600 usb and linux usb scanner module
From: ####@####.#### Date: 1 May 2000 22:32:03 -0000 Message-Id: <200005012232.AAA00497@smtp2.home.se> Why can't someone just read the part numbers inside the IBM Ideascan 2000 so that we will know if it's a primax scanner or not? _________________________________________________________ En adress för livet registrerar du på http://www.home.se/ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Primax 9600 usb and linux usb scanner module
From: Bryn Jeffries ####@####.#### Date: 2 May 2000 07:37:22 -0000 Message-Id: <20000502083723.A30433@thelonious.new.ox.ac.uk> ####@####.#### ####@####.#### wrote: > Why can't someone just read the part numbers inside the IBM Ideascan > 2000 so that we will know if it's a primax scanner or not? That would require someone happily opening up their machine, I guess. For the moment this isn't the problem, anyway. The Primax USB scanner currently won't be detected because of these two, rather than one, IN endpoints (whatever they are). I don't have enough pragramming to work out how to stop the usb scanner code from ignoring this extra line, and I also don't know whether it's actually required. Does anyone? B. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |