There are always some little differences between bluetooth cards. Not having all of them to test, I cannot garantee all of the supported cards will work without problems...
OK, here's where I am with getting my rev of Bluemonkey card fixed.
I have found that if I take the binary module 'bluez.o' from
http://community.zaurus.com/download.php/5...2.4.18d_arm.ipk, rename the symlink on the Cacko ROM, rmmod the existing bluez driver, copy in the aforesaid driver, depmod -a then plug the card everything works well - I can eject the card without any of the lockups mentioned whatsoever and it seems pretty bullet proof.
Unfortunately the bluez.o from this version doesn't seem to initialize something particularly well so following a reboot if I insert the card I get a 0 MAC address on hciconfig . - maybe something isn't getting called to initialize the card here... hmmm.
Sooo, it would seem that an examination of the Bluez source - probably hci_core from the community site and the source of the Cacko ROM would probably let me nail this.
I have the Cacko Kernel tree all patched up and ready to go.
Can't locate the source for the Rev D. driver on the community site though. There seems to be only Rev A source on this site.
Any ideas where I may obtain the source/patch sets for this rev ?
I'm hazarding a wild guess that Rev. D on the community site is based on patch-2.4.18-mh10. Whereas Cacko is patch-2.4.18-mh11, is this correct ?