site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com Why do you want to connect to the MightyMouse ? ... Marco On Jan 17, 2007, at 12:55 AM, Moritz Gmelin wrote: Hi, Thanks _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... I am not certain, but my guess is that it is all because of speed, the HID driver kext is designed to match on channel with PSM 0x11, which means that as soon as that channel shows up the kext will try to attach to it. Also an L2CAP channel (RFCOMM channels too) can have only one client. So the first client to connect wins. Simply openL2CAPChannelSync is faster than openL2CAPChannelAsync (since openL2CAPChannelAsync is a notification from kernel to user space) so with openL2CAPChannelSync you win with openL2CAPChannelAsync the kext wins. if I want to open a L2CAP connection to my MightyMouse on channel 0x11, it works if I call openL2CAPChannelSync however, if I try to open the same connection using openL2CAPChannelAsync (Async instead of Sync) my l2capChannelOpenComplete method of the listener gets called with an error. Can anyone explain why this happens ? The same seems to apply to Wii remote control devices and possibly all HDI devices. Moritz _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/mpontil% 40apple.com This email sent to mpontil@apple.com This email sent to site_archiver@lists.apple.com