Re: PSM Sign Extension Problem
Re: PSM Sign Extension Problem
- Subject: Re: PSM Sign Extension Problem
- From: Michael Larson <email@hidden>
- Date: Thu, 21 Nov 2002 15:46:00 -0800
This is correct. We will fix this for the next release. In the
meantime, we'll be looking into a workaround we can provide for your
use until the next version is released.
Thanks,
-larson
On Thursday, November 21, 2002, at 03:26 AM, Eric Kolotyluk wrote:
There seems to be a problem with L2CAP PSM values higher than 127
returned from IOBluetoothSDPServiceRecord class getL2CAPPSM: method.
We have a device that uses a PSM of 12F1 but getL2CAPPSM returns FFF1.
I confirmed this with both NSLog and the debugger. To be sure we used
another programmable Bluetooth device with a lower PSM of 1 which
returned properly, but when we programmed it for 12F1 my Apple code
showed FFF1 again.
We suspect that the code may only be reading an 8-bit quantity
somewhere from the service record and sign extending it when returning
the 16-bit PSM value. Could someone from Apple please verify this?
_______________________________________________
bluetooth-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/bluetooth-dev
Do not post admin requests to the list. They will be ignored.