public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Nick Pelly <npelly@google.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Tools for AVDTP / AVCTP qualification
Date: Tue, 06 Jan 2009 02:18:10 +0100	[thread overview]
Message-ID: <1231204690.13304.7.camel@californication> (raw)
In-Reply-To: <35c90d960901051647x3166e1e2g27cf53c19df48246@mail.gmail.com>

Hi Nick,

> > Do there exist any tools to help pass Bluez AVDTP and AVCTP stack qualification?
> >
> > Looking at the test spec it seems some command line tools might be
> > handy. I am thinking along the lines of l2test, hcitool etc. I'll be
> > writing some similar for AVDTP and AVCTP unless there are already some
> > floating around?
> 
> Following up on this old thread,
> 
> The AVDTP and AVCTP SIG test specification documents explain a
> complex, automated testing environment where an 'upper tester' makes
> method or IPC calls into your stack to cause it to run through various
> AVDTP/AVCTP request/responses with the 'lower tester'. This was what
> my original email was about - if there were tools to interface with
> the upper tester.
> 
> What those documents do not explain is that it seems for A2DP and
> AVRCP products you can submit frontline sniff traces of the PTS tests
> as evidence of AVDTP/AVCTP compatibility. So in our case we don't need
> the tools. Hope this helps others trying to wade through SIG
> bureaucracy.

so since the Frontline software can read BTSnoop format HCI based
traces, it would be nice if we can sent these in. Especially since
hcidump can write these natively. So no complex setups.

Regards

Marcel



      reply	other threads:[~2009-01-06  1:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23  0:13 Tools for AVDTP / AVCTP qualification Nick Pelly
2008-12-23  0:50 ` Marcel Holtmann
2009-01-06  0:47 ` Nick Pelly
2009-01-06  1:18   ` Marcel Holtmann [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=1231204690.13304.7.camel@californication \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=npelly@google.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