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)
> > Usually a device should NAK the polling, if it has nothing to say.
> > But here it doesn't say anything...
>
> Isn't it the camera sending these interrupts?
No, 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.
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?).
--
Bye
Georg Acher, [EMAIL PROTECTED]
http://www.in.tum.de/~acher/
"Oh no, not again !" The bowl of petunias
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
