[Barry-devel] 8700r testing

[Steve Paras-C. <st...@fa...>]

Here's the results I get from btool on the 8700r.  Looks like it may be confused
by previous incarnations (I plug and unplug alot).

root@yu:/usr/src/barry-0.0.1 # src/btool -t
libusb: setting debugging level to 9 (on)
libusb: [usb_os_init:879] found USB VFS at /proc/bus/usb
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/007
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/006
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/005
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/004
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/003
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/002
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/001
libusb: [usbi_os_find_busses:450] skipping non bus dir devices
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/007
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/006
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/005
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/004
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/003
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/002
libusb: [usbi_os_find_busses:469] found bus dir /proc/bus/usb/001
libusb: [usbi_os_find_busses:450] skipping non bus dir devices
libusb: [create_new_device:558] found device 001 on /proc/bus/usb/007
libusb: [create_new_device:558] found device 001 on /proc/bus/usb/006
libusb: [create_new_device:558] found device 001 on /proc/bus/usb/005
libusb: [create_new_device:558] found device 001 on /proc/bus/usb/004
libusb: [create_new_device:558] found device 004 on /proc/bus/usb/004
libusb: [create_new_device:558] found device 001 on /proc/bus/usb/003
libusb: [create_new_device:558] found device 001 on /proc/bus/usb/002
libusb: [create_new_device:558] found device 001 on /proc/bus/usb/001
libusb: [device_is_new:498] device /proc/bus/usb/007/001 previously existed, but
mtime has changed
libusb: [device_is_new:498] device /proc/bus/usb/006/001 previously existed, but
mtime has changed
libusb: [device_is_new:498] device /proc/bus/usb/005/001 previously existed, but
mtime has changed
libusb: [device_is_new:498] device /proc/bus/usb/004/001 previously existed, but
mtime has changed
libusb: [device_is_new:498] device /proc/bus/usb/004/004 previously existed, but
mtime has changed
libusb: [device_is_new:498] device /proc/bus/usb/003/001 previously existed, but
mtime has changed
libusb: [device_is_new:498] device /proc/bus/usb/002/001 previously existed, but
mtime has changed
libusb: [device_is_new:498] device /proc/bus/usb/001/001 previously existed, but
mtime has changed
BError caught: Probe: Unexpected reponse data in parse


And here's the messages entries (looks ok to me; a plug in and two btool runs)

Dec 29 19:40:43 localhost kernel: usb 4-2: new full speed USB device using
ohci_hcd and address 4
Dec 29 19:59:51 localhost kernel: atkbd.c: Keyboard on isa0060/serio0 reports
too many keys pressed.
Dec 29 20:01:18 localhost kernel: usb 4-2: reset full speed USB device using
ohci_hcd and address 4
Dec 29 20:01:23 localhost kernel: usb 4-2: usbfs: interface 0 claimed while
'btool' sets config #1
Dec 29 20:03:08 localhost kernel: usb 4-2: reset full speed USB device using
ohci_hcd and address 4
Dec 29 20:03:13 localhost kernel: usb 4-2: usbfs: interface 0 claimed while
'btool' sets config #1


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.