From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <1148998994.11251.9.camel@localhost> References: <822EACFA-537D-4382-BA97-4192E5EBCF4A@pepper.com> <1148908353.31689.28.camel@localhost> <1148998994.11251.9.camel@localhost> Message-Id: From: Michael Frey Date: Tue, 30 May 2006 10:58:39 -0400 To: BlueZ development Subject: Re: [Bluez-devel] Bluez Bluetooth certification tests? Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1289261202==" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net --===============1289261202== Content-Type: multipart/alternative; boundary=Apple-Mail-4-1042711155 --Apple-Mail-4-1042711155 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Hi Marcel, I think I am understanding. Couple of more things. We use a certified Bluetooth module (Insung module using a CSR chip) along with Bluez. Do you know what testing will we need to do as a product to get certification? And how do we reference the Bluez stack in our certification? Thanks, Michael On May 30, 2006, at 10:23 AM, Marcel Holtmann wrote: > 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 --Apple-Mail-4-1042711155 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 Hi Marcel,

I think I am = understanding.=A0 Couple of more things.
We = use a certified Bluetooth module (Insung module using a CSR chip) along = =A0with Bluez. Do you know what testing will we need to do as a product = to get certification? And how do we reference the Bluez stack in our = certification?

Thanks,
Michael


On May 30, 2006, at = 10:23 AM, Marcel Holtmann wrote:

Hi Michael,

Are = there any resulting test harness or supporting code from TomTom's =A0
=A0 Or does the = fact the if someone uses the Bluez stack, they =A0
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
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
=

= --Apple-Mail-4-1042711155-- --===============1289261202== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============1289261202== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel --===============1289261202==--