PrefaceI know my way around a bash shell... a bit... but I am a n00b when it comes to Kernal hacking and Linux Device drivers. I swallowed the first 3-chapters of the Linux Device Drivers, Edition 3 - PDF, so I know a bit more about it than I did at the start of the week, but still not so much.Please, if you state 'just do x and then y', where x is something like 'download the latest kernel' and y is something like 'build it', kindly link to a tutorial or guide on how to do x and y, because n00b.SystemDistribution: Ubuntu 14.04.4 LTS, Trusty TahrKernel: 4.4.0-47-GenericProblemI am trying to replace the kernel btusb driver with the Bluetopia USB BT driver SS1BTUSB (Driver source and build files from CodeAurora), because I am trying to learn more about the Bluetopia Bluetooth stack implementation, and this is the first step to being able to do that.I can successfully build the SS1BTUSB Kernel module and install it.$ sudo insmod SS1BTUSBM.ko$ lsmod | grep SS1BTUSBSS1BTUSBM              32768  0And, following the instructions from the lwn.net article, I can unbind the devices attached to the btusb driver.$ ls /sys/bus/usb/drivers/btusb1-1.5:1.0  1-1.5:1.1  bind  module  new_id  remove_id  uevent  unbind$ sudo -i# echo 1-1.5:1.0 > /sys/bus/usb/drivers/btusb/unbind# echo 1-1.5:1.1 > /sys/bus/usb/drivers/btusb/unbind-bash: echo: write error: No such device# ls /sys/bus/usb/drivers/btusbbind  module  new_id  remove_id  uevent  unbindI am not sure why unbinding the second device causes the error but the result is the devices are unbound from the btusb driver.However, when I try and bind these devices to the SS1BTUSB1 driver, I get the same error.# echo 1-1.5:1.1 > /sys/bus/usb/drivers/SS1BTUSB/bind-bash: echo: write error: No such device# echo 1-1.5:1.0 > /sys/bus/usb/drivers/SS1BTUSB/bind-bash: echo: write error: No such deviceIt seems that the 'No such device' error is fairly generic and could mean any number of things, suggestions on how to debug/diagnose this issue would be greatly appreciated. Random Notes(May or may not help diagnose the problem).The btusb driver is used by other drivers - could be related.$ lsmod | grep btusbbtusb                  45056  0btrtl                  16384  1 btusbbtbcm                  16384  1 btusbbtintel                16384  1 btusbbluetooth             516096  25 bnep,btbcm,btrtl,btusb,rfcomm,btintelUSB info on the Bluetooth USB dongle...$ lsusb.Bus 001 Device 003: ID 0a12:1243 Cambridge Silicon Radio, Ltd.It's actually a CSR8675 Headset Development Board configured as a BT dongle (this bit I know about), so it's details look a bit screwy...$ usb-devices.T:  Bus=01 Lev=02 Prnt=02 Port=04 Cnt=01 Dev#=  3 Spd=12  MxCh= 0D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1P:  Vendor=0a12 ProdID=1243 Rev=20.32S:  Product=CSR8675 USB HeadsetS:  SerialNumber=ABCDEF0123456789C:  #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=500mAI:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusbI:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusbI:  If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none).But it is a functional Bluetooth HCI device.
Unbind/bind new Bluetooth Device Driver - Ubuntu 14.04 Trust Tahr
ubuntu;drivers;bluetooth;usb device