All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daryl Van Vorst" <dvpub@telus.net>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] BlueZ Qualification
Date: Mon, 24 Feb 2003 16:27:18 -0800	[thread overview]
Message-ID: <002201c2dc64$a7c96830$1a01010a@baked> (raw)

[-- Attachment #1: Type: text/plain, Size: 414 bytes --]

There was some discussion about Bluetooth qualification almost a year ago.
Has there been any news since that discussion?
 
Are there any products using the BlueZ stack that have been tested and
approved by the BQB (Bluetooth Qualification Body)?
 
To aid in certification are there ICS (implementation conformance
specifications/statements) for individual profiles supported by BlueZ?
 
Thanks,
 
-Daryl.
 
 
 
 

[-- Attachment #2: Type: text/html, Size: 1807 bytes --]

             reply	other threads:[~2003-02-25  0:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25  0:27 Daryl Van Vorst [this message]
2003-02-27 21:09 ` [Bluez-devel] BlueZ Qualification Max Krasnyansky
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='002201c2dc64$a7c96830$1a01010a@baked' \
    --to=dvpub@telus.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.