From: Brian Gix <bgix@codeaurora.org>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Read Characteristic Value vs. Read Long Characteristic Values
Date: Tue, 08 Feb 2011 12:58:04 -0800 [thread overview]
Message-ID: <4D51AE5C.5020006@codeaurora.org> (raw)
In-Reply-To: <AANLkTi=6fNu_2jH8_KijR-a_U+DbkRiz6C667N7NBQLV@mail.gmail.com>
Hi Anderson,
On 2/8/2011 12:46 PM, Anderson Lizardo wrote:
> Hi Brian,
>
> On Wed, Jan 26, 2011 at 4:57 PM, Brian Gix<bgix@codeaurora.org> wrote:
>> I will talk to the PTS guys at UPF, and make sure that the PIXIT lists
>> are setup such that the tests required for qualification correctly
>> mandate the correct subset of test cases as required by the ruling
>> specification.
>
> Did you manage to get some input from PTS guys on these tests? I did
> not check the recently released 4.2.0 yet.
>
> Regards,
I was talking to the guy who wrote most of the GATT tests, and he said
that the test for "Read Long" in particular should Pass wether it was
initiated with a standard READ or READ_BLOB. He said that if the test
does not work that way, to send him a PTS log of the particular test
session that did not work as expected (that test or any other).
I will try to get the exact email address to use for PTS log submissions
and get back to you.
--
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
prev parent reply other threads:[~2011-02-08 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 19:07 Read Characteristic Value vs. Read Long Characteristic Values Anderson Lizardo
2011-01-25 19:46 ` Brian Gix
2011-01-26 13:33 ` Anderson Lizardo
2011-01-26 13:58 ` Anderson Lizardo
2011-01-26 14:54 ` Anderson Lizardo
2011-01-26 17:59 ` Brian Gix
2011-01-26 18:28 ` Anderson Lizardo
2011-01-26 19:57 ` Brian Gix
2011-02-08 20:46 ` Anderson Lizardo
2011-02-08 20:58 ` Brian Gix [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D51AE5C.5020006@codeaurora.org \
--to=bgix@codeaurora.org \
--cc=anderson.lizardo@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).