Hi. 2011/6/8 Santiago Carot <sancane@xxxxxxxxx>: > Hello Claudio. > > 2011/6/8 Claudio Takahasi <claudio.takahasi@xxxxxxxxxxxxx>: >> Hi Santiago and Elvis, >> >> Read clock is not implemented in the management interface. Does it >> break something important in the health plug-in? >> 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. Regards. > > Read clock is only required for Clock Shynchronization Protocol (CSP) > in MCAP, but CSP is not mandatory for HDP and although this feature > was implemented in MCAP is not used in the Health Plugin so it won't > break the API. > >> I am not aware when hciops will be dropped, but the fact is: if the >> system uses mgmtops instead of hciops health will not work properly. >> > > Well, as far as I know, only MCAP uses it for CSP and it's an optional > part in the specification so it won't a severe problem for health > applications. > >> BR, >> 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
