The config option CONFIG_USB_MUSB_TUSB6010 breaks the musb driver on anything that is not the tusb 6010, including the beaglebone.
Turning off that option in the kernel config should fix it, or including the upstream patches that make it runtime detect what type of device it is on would work too. The upstream patches I believe are: 9d506fc6d2cdafdec5ce605036f5eeec9fd59657 usb: musb: Populate new IO functions for tusb6010 1b40fc57a517878cf4c2e16ce29cc9a066dc1064 usb: musb: Change to use new IO access d026e9c76aac3632af174cf02d5c94defa5e6026 usb: musb: Change end point selection to use new IO access 8a77f05aa39be879535f22a9757e703581fa1392 usb: musb: Pass fifo_mode in platform data If the kernel package in jessie was to include those patches, or just change the config option on arm, it ought to fix the beaglebone's usb problems. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
