Hello, > > > virtualbox and then running either usbmon or Wireshark on your Linux > > > system should work just fine. > > > > O.K., here's what I found: running windows in virtualbox first then > > shutting it down again: the adapter works in linux too until the next > > reboot (still have to load the module and echo the ID to new_ID because > > of the adapter not reconigzed by the actual bt module) > > Doing a capture with wireshark on usb port 2 gives me the capture file > > attached. > > so there is clearly some binary download in the capture file. It will > most likely match the files that a referenced in the .inf file. However > I am not reverse engineering this stuff for anybody. Someone else has to > do that job. based on the trace and the .hex files I extracted from the Windows driver package I wrote a simple python rampatch downloader script. I also started writing a downloader kernel module. I have two questions though. Is there a need for a driver module at all? The script seems to work well, so I think it would be sufficient to write a statically linked libusb based binary downloader and distribute it along with the rampatch files and an udev rule file. If the module is needed for whatever reason, is there a way to implement it using btusb HCI interface functions? The rampatch download process is basically a series of HCI commans sent to control or bulk out endpoint. I could of course implement the payload packaging myself, but I feel somehow, that a cleaner solution would be to use some common subsystem mechanism. Regards David -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
