Georg Acher wrote:
>
> On Wed, Apr 19, 2000 at 04:48:02PM +0000, Mikael Nystr�m wrote:
> > Georg Acher wrote:
>
> > > There seems to be a problem with the 128ms-interrupt. Since full
> > > debugging is not enabled, it is not clear, which device causes this.
> >
> > Oki, I search some file but couldn't find out how to enable "full"
> > debugging, I turned on "verbose mode" hovever, here is a new run:
>
> Remove the comment-slashes in usb-uhci, function process_interrupt,
> around line 2274, (now: '//uhci_show_td (desc); '). I assume that the
> device ID that gets printed is the one of the camera (but just to make
> sure what the actual error code is)
Apr 19 19:11:37 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
1600
Apr 19 19:11:37 veiron kernel: usb-uhci-debug.h: TD @
c1e618a0/01E618A0, MaxLen=00 DT1 EP=3 Dev=2 PID=( IN ) buf=0797ecde
Apr 19 19:11:37 veiron kernel: usb-uhci-debug.h: Len=00 e3 SPD IOC
Stalled Babble
Apr 19 19:11:37 veiron kernel: usb-uhci-debug.h: Link points to TD @
01e61560, Breadth first
Repeated severel times (just the frame# differs).
/proc/bus/usb/devices
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.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=e000
C:* #Ifs= 1 Cfg#= 1 Atr=40 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= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=32 #Cfgs= 1
P: Vendor=04a9 ProdID=3043 Rev= 0.01
S: Manufacturer=Canon Inc.
S: Product=PowerShot S20
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff 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= 64 Ivl= 96ms
However I tried the "alternative" driver uhci.c, and it works with no
problem, not even the "delay" exist when I try to shutdown the camera:
Apr 19 18:45:33 veiron kernel: uhci.c: USB UHCI at I/O 0xe000, IRQ 9
Apr 19 18:45:33 veiron kernel: uhci.c: detected 2 ports
Apr 19 18:45:33 veiron kernel: usb.c: new USB bus registered, assigned
bus number 1
Apr 19 18:45:33 veiron kernel: usb.c: USB new device connect, assigned
device number 1
Apr 19 18:45:33 veiron kernel: Product: USB UHCI Root Hub
Apr 19 18:45:33 veiron kernel: SerialNumber: e000
Apr 19 18:45:33 veiron kernel: hub.c: USB hub found
Apr 19 18:45:33 veiron kernel: hub.c: 2 ports detected
Apr 19 18:45:33 veiron kernel: usb.c: registered new driver usbscanner
Apr 19 18:45:33 veiron kernel: scanner.c: USB Scanner support
registered.
Apr 19 18:45:38 veiron kernel: usb.c: USB new device connect, assigned
device number 2
Apr 19 18:45:38 veiron kernel: Manufacturer: Canon Inc.
Apr 19 18:45:38 veiron kernel: Product: PowerShot S20
Apr 19 18:45:38 veiron kernel: scanner.c: probe_scanner: User specified
USB scanner -- Vendor:Product - 4a9:3043
Apr 19 18:45:53 veiron kernel: usb.c: USB disconnect on device
2
However it is much slower. My testfile 2593175bytes long took 12s to
transfer with uhci.c and only 8.5s with usb-uhci.c (using 5k blocks in
both cases).
> interrupts in USB-speech are actually scheduled polling transfers,
> initiated by the PC. The device is not able to do anything without a
> request.
> > If so who is responsible for taking care of the information eventually
> > carried along whith the interrupt, scanner.c?
> Yes, but at the current state (pre5) it looks like nothing useful is done
> with the information, so at the moment the error message is only annoying,
> it has no effect on the other endpoints.
But in that that case the usb driver keeps the camera busy (causing the
delay at "power off", not only printing annoying messages in logfile?
> Can anybode else with this camera and a deeper knowledge of the scanner
> driver look into this? To me it looks like the camera doesn't like the
> polling (does it need some enable for that?).
I'll be very happy if anyone can help me finding out why my camera
dislike the usb-uhci driver, where do I start?
Mikael Nystr�m
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
