From: Max Krasnyansky <maxk@qualcomm.com>
To: "Daryl Van Vorst" <dvpub@telus.net>, <bluez-devel@lists.sourceforge.net>
Cc: Halam.Rose@7layers-UK.com, bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-devel] BlueZ Qualification
Date: Thu, 27 Feb 2003 13:09:57 -0800 [thread overview]
Message-ID: <5.1.0.14.2.20030227125343.023513a0@mail1.qualcomm.com> (raw)
In-Reply-To: <002201c2dc64$a7c96830$1a01010a@baked>
At 04:27 PM 2/24/2003, Daryl Van Vorst wrote:
>There was some discussion about Bluetooth qualification almost a year ago. Has there been any news since that discussion?
Several people (from different companies) seem to be working on writing test scripts.
But there is no centralized effort.
>Are there any products using the BlueZ stack that have been tested and approved by the BQB (Bluetooth Qualification Body) ?
Not that I know of.
>To aid in certification are there ICS (implementation conformance specifications/statements) for individual profiles
>supported by BlueZ ?
Not yet. A lot of people are interested but no one has made any moves so far.
It's good that you brought this issue up again. Because "7 layers UK" (a BQB company)
expressed some interest in carrying out qualification work on BlueZ without charging
any fees as part of their marketing.
So it's a good time to unite the efforts. We should probably start some project where
people could contribute test scripts and stuff.
I'm pretty sure that Sony and Inventel have done some work on it.
Any comments/suggestions/ideas from you guys ?
Thanks
Max
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-02-27 21:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 0:27 [Bluez-devel] BlueZ Qualification Daryl Van Vorst
2003-02-27 21:09 ` Max Krasnyansky [this message]
2003-02-28 9:01 ` David LIBAULT
2003-02-28 9:38 ` Marcel Holtmann
2003-02-28 10:49 ` BlueZ Qualification and 7 Layers UK Halam Rose
2003-02-28 11:10 ` [Bluez-devel] " David LIBAULT
2003-02-28 20:58 ` Max Krasnyansky
2003-03-03 16:03 ` Marcel Holtmann
2003-02-28 20:48 ` [Bluez-devel] BlueZ Qualification Max Krasnyansky
2003-02-28 20:28 ` Max Krasnyansky
2003-02-28 20:46 ` Max Krasnyansky
2003-03-03 15:48 ` Marcel Holtmann
2003-03-03 18:06 ` David LIBAULT
2003-03-06 22:06 ` Max Krasnyansky
2003-03-07 8:47 ` David LIBAULT
2003-03-07 17:44 ` Max Krasnyansky
2003-03-25 1:51 ` Max Krasnyansky
2003-03-05 4:35 ` Takashi Sasai
2003-03-06 22:11 ` Max Krasnyansky
2003-03-06 21:33 ` Max Krasnyansky
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=5.1.0.14.2.20030227125343.023513a0@mail1.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=Halam.Rose@7layers-UK.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-users@lists.sourceforge.net \
--cc=dvpub@telus.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