Return-Path: Subject: Re: Read Characteristic Value vs. Read Long Characteristic Values From: Brian Gix To: Anderson Lizardo Cc: BlueZ development In-Reply-To: References: <1295984785.2656.98.camel@ubuntuLab1> Content-Type: text/plain; charset="UTF-8" Date: Wed, 26 Jan 2011 09:59:22 -0800 Message-ID: <1296064762.2656.137.camel@ubuntuLab1> Mime-Version: 1.0 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Anderson, On Wed, 2011-01-26 at 09:58 -0400, Anderson Lizardo wrote: > On Wed, Jan 26, 2011 at 9:33 AM, Anderson Lizardo > wrote: > > Looks like more a PTS bug, but makes me wonder if it is not better for > > BlueZ to have separate procedures instead of this "automatic" usage of > > read blob request ? > > BTW, the test which presented this issue with sending spurious read > blob request is named "Read Characteristic Descriptors – by client". I > also can see that the behavior you implemented satisfies both "Read > Long Characteristic Value - by client" and "Read Long Characteristic > Descriptor - by client" tests. All theses tests come from the GATT TS > document. Can you tell me the specific Test Case number(s) that you are having difficulty testing? I do not have a current release of the PTS tool available to me at this time, although I do know that PTS is developed in parallel, and is just as prone to bugs as the rest of us. I should be able to test this stuff against the PTS guys at UPF week after next, and talk to the guys who are writing it. Thanks, -- Brian Gix bgix@codeaurora.org Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum