From: Marcel Holtmann <marcel@holtmann.org>
To: Balaji Palaniswami <balaji_palaniswami@yahoo.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Bluez Certification
Date: Tue, 07 Jul 2009 10:40:04 -0700 [thread overview]
Message-ID: <1246988404.3384.13.camel@localhost.localdomain> (raw)
In-Reply-To: <454943.43647.qm@web95403.mail.in2.yahoo.com>
Hi Balaji,
> I had a couple of questions related to the BQB qualification
> of the Bluez stack and was wondering if someone could help with the same
>
> The BQB certification is of two types – profile and host.
> Basically we are trying to get the BQB profile qualification for a BT
> dongle.
>
> There are a number of companies that have done the BQB host
> side certification for the Bluez stack. Ideally we would like to leverage the
> BT host certification done by the other companies for the host side and simply do a profile cert for our device.
>
> The questions I have are the following:
> Is 1) Is it possible to reuse a certification done by someone
> else? Has this been done before? ( The Helsinki developer meeting minutes from
> 2008 seem to suggest this has been done before)
yes, it is possible if kernel version and source code are matching. And
if the BlueZ source code is matching.
> 2) If it is possible then what is the procedure for the
> same?
Just do it. The Bluetooth SIG has a procedure for it. It is a little bit
confusing, but should still work.
> 3) Is there a particular BQ ID that has been made
> available for other people to use?
There are few, but it always depends on 1) and it if matches.
> 4) Have any devices been qualified for Bluetooth 2.1 with
> Bluez?
Yes. Not sure if all of them are listed yet.
Regards
Marcel
next prev parent reply other threads:[~2009-07-07 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 8:47 Bluez Certification Balaji Palaniswami
2009-07-07 17:40 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-13 13:18 Cesare Magri
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=1246988404.3384.13.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=balaji_palaniswami@yahoo.com \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).