Hi, On Thu, Jun 09, 2011, Elvis Pfutzenreuter wrote: > > Coming back to this issue. I'm not caught up with this stuff and I > > dont know if there are any special reason to not provide a read clock > > functionality in the bluetooth API. although I think it's a pity to > > restrict MCAP features after the good work Elvis did in CSP. > > More to the point, could we implement HCI read clock for mgmt interface? Or > it simply won't have read clock by design? There's no obvious reason why it couldn't have it. However other means should be considered too, e.g. would it be cleaner to get the info directly through the socket (using a socket option or something similar)? Or was this already considered when the HCI socket solution was implemented? 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
