Hi Mike, > After upgrade the kernel to 2.6-next branch, it does initiate the > just-work, no-bonding operation and it does work.(no more endless > loop). However, I found another issue is that during discovery, the > client will try to read every characteristic it found, regardless the > property setting. This causes "Read Not Permitted" error response for > some characteristic that does not allowed to be read (like the > alert-level). I am not sure why the discovery process wants to read > the characteristic value though, that should be invoked by profile > later when needed, > > Regards, > > Mike The Generic Attribute is still experimental. DiscoverCharacteristics method returns after discovering all characteristic declarations, characteristic values and descriptor are read in "background". "Read Not Permitted" needs to be fixed. Feel free to send a patch for it. The characteristic value is required due the GetProperties method of the characteristic "object". At the moment, the characteristics storage is not being used properly. For example, Proximity could read the handle from the storage if available. Regards, Claudio. -- 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
