Hi!
I'm a newbee on USB and also (like David Brownell) have problems with
warnings in
/var/log/messages
Apr 19 13:38:18 veiron kernel: usb.c: registered new driver usbscanner
Apr 19 13:38:18 veiron kernel: scanner.c: USB Scanner support
registered.
Apr 19 13:38:51 veiron kernel: scanner.c: open_scanner(0): invalid
scn_minor
Apr 19 13:39:01 veiron kernel: usb.c: USB new device connect, assigned
device number 2
Apr 19 13:39:01 veiron kernel: scanner.c: probe_scanner: User specified
USB scanner -- Vendor:Product - 4a9:3043
Apr 19 13:39:04 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
64
Apr 19 13:39:04 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
192
Apr 19 13:39:04 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
320
Apr 19 13:39:04 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
448
Apr 19 13:39:05 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
576
Apr 19 13:39:05 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
704
Apr 19 13:39:05 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
832
and continuing with 8 new lines each second....
Exactly whats has happened when the kernel generates this messages?
They start as soon as my program have made some handshaking with the
camera.
File transfers and everything work smoothly, but these interrupts seems
to come reguraly, even during long file transfers.
It seems like these comes approxematly as ofen as the windows driver
accesses
the windows call IOCTL_WAIT_ON_DEVICE_EVENT "Returns information about
an event occuring on a USB interrupt pipe.".
(http://www.microsoft.com/ddk/ddkdocs/win2k/stifnc_74x3.htm for details)
My little testprogram is written in perl using a lightly modified
scanner.c (two new extended versions of PV8630_IOCTL_(IN/OUT)REQUESTS.
Must scanner.c be modified further to handel these requests?
Mikael Nystr�m
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
