All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:05:36 +0200	[thread overview]
Message-ID: <1149001536.11251.12.camel@localhost> (raw)
In-Reply-To: <D86403B9-8AD2-4EC8-AE3B-02FE7A4F2C0A@pepper.com>

Hi Michael,

> 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?

I actually have no idea. The BQB took care of this.

Regards

Marcel





_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2006-05-30 15:05 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
2006-05-30 14:58       ` Michael Frey
2006-05-30 15:05         ` 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=1149001536.11251.12.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 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.