From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluez Bluetooth certification tests?
Date: Tue, 30 May 2006 16:23:14 +0200 [thread overview]
Message-ID: <1148998994.11251.9.camel@localhost> (raw)
In-Reply-To: <CB055E3B-083D-4B4A-B42C-2ADB2E3DEFC6@pepper.com>
Hi Michael,
> Are there any resulting test harness or supporting code from TomTom's
> effort? Or does the fact the if someone uses the Bluez stack, they
> are by default certified?
you can use the current BlueZ qualification to qualify your own product.
It will save you a lot of time, because most test have are already been
done. And I think we spent 4 days with the L2CAP, RFCOMM and SDP testing
and you don't wanna do it again normally.
At some point the BlueZ qualification must be updated to PRD 2.0, but I
only wanna do that after the Lisbon specification has been released. It
makes no real sense to do it again now. With PRD 2.0 it should also
include some kind of HCI qualification so you basically don't even have
to re-qualify your hardware. However I haven't fully looked into the new
qualification program. I will do that when the next specification
version gets public and I have found a sponsor for it. We still have to
pay the listing fee.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-30 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 13:08 [Bluez-devel] Bluez Bluetooth certification tests? Michael Frey
2006-05-29 13:12 ` Marcel Holtmann
2006-05-30 14:06 ` Michael Frey
2006-05-30 14:23 ` Marcel Holtmann [this message]
2006-05-30 14:58 ` Michael Frey
2006-05-30 15:05 ` Marcel Holtmann
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=1148998994.11251.9.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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