Hi Andre, On Wed, Mar 20, 2013, Andre Guedes wrote: > HCI Inquiry command causes the controller to enter in inquiry mode. A > successful Command Status Event for this command means the the > controller is running the inquiry procedure therefore the HCI Inquiry > command has completed. The Inquiry Complete Event, on the other hand, > means the inquiry _procedure_ (not the HCI command) has completed. It would be good if you could show exact quotes from the core specification instead of making stuff up. Here's an exact quote from the core spec (page 706) regarding events generated by the Inquiry command: "No Command Complete event will be sent by the BR/EDR Controller to indicate that this command has been completed. Instead, the Inquiry Complete event will indicate that this command has been completed." That's quite the opposite of what you're claiming, with no references to the procedure completion but only the command completion. This makes me feel like you're trying to persuade us to a particular technical outcome that suits your needs with the help of misleading/inaccurate information. It might well be in our best interest to keep processing our request/command queue based on command status events (essentially treating the commands as completed) but let's at least be honest about what the exact wording in the core specification is. Johan -- 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
