Linux-Bluetooth Archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "Naga Bhavani Akella (QUIC)" <quic_nakella@quicinc.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	 "Mohammed Sameer Mulla (QUIC)" <quic_mohamull@quicinc.com>,
	 "Anubhav Gupta (QUIC)" <quic_anubhavg@quicinc.com>,
	"Harish Bandi (QUIC)" <quic_hbandi@quicinc.com>
Subject: Re: Query regarding BlueZ Stack Certification
Date: Wed, 8 May 2024 10:15:58 -0400	[thread overview]
Message-ID: <CABBYNZK1XfX+ug9+ktSTpQKG03LBK2_h4UxUuF3w14-8k4t3gw@mail.gmail.com> (raw)
In-Reply-To: <SA2PR02MB782004DF03924528761D402492E52@SA2PR02MB7820.namprd02.prod.outlook.com>

Hi,

On Wed, May 8, 2024 at 2:35 AM Naga Bhavani Akella (QUIC)
<quic_nakella@quicinc.com> wrote:
>
> Hi Team,
>
> Could you please help us with these questions
>
> 1) We are looking for some information on BLUEZ Stack Certification.
>      Is there any existing BlueZ stack certification ( we are using BlueZ 5.65 ) already done which we can reuse,
>      if so can you please share QDID ?
> 2) If someone has to do certification from the start,
>     are there any tools or apps available on bluez which can be used to run protocol/profile test cases against PTS ?

You can find the previous qualifications done in the following github
discussion, we are also discussing how we could establish a more
generic Host Subsystem listing so feel free to contribute:

https://github.com/orgs/bluez/discussions/817

> Thanks and Regards,
> Bhavani
>


-- 
Luiz Augusto von Dentz

      reply	other threads:[~2024-05-08 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08  6:34 Query regarding BlueZ Stack Certification Naga Bhavani Akella (QUIC)
2024-05-08 14:15 ` Luiz Augusto von Dentz [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=CABBYNZK1XfX+ug9+ktSTpQKG03LBK2_h4UxUuF3w14-8k4t3gw@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=quic_anubhavg@quicinc.com \
    --cc=quic_hbandi@quicinc.com \
    --cc=quic_mohamull@quicinc.com \
    --cc=quic_nakella@quicinc.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).