Linux bluetooth development
 help / color / mirror / Atom feed
From: Takashi Sasai <sasai@sm.sony.co.jp>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
	david.libault@inventel.fr, Daryl Van Vorst <dvpub@telus.net>,
	bluez-devel@lists.sourceforge.net, Halam.Rose@7layers-UK.com
Subject: Re: [Bluez-devel] BlueZ Qualification
Date: Wed, 05 Mar 2003 13:35:03 +0900	[thread overview]
Message-ID: <8765qysa6g.wl@maple.sm.sony.co.jp> (raw)
In-Reply-To: <1046706518.14907.133.camel@linux>

Hi,

> People that already have some experiences in qualification (and
> especially BlueZ) should start now sharing their results with us, so we
> can start planing the next step.

I checked a little ten months ago, but unfortunately I didn't need to
get qualification for now. However I can help and comment by
experiences personally.

Finally it seems that it's duty to sell products in order to get
interoperability and good quality. At least, any companies must do
testing for application profile using final products and get
quarification itself.

I don't know it's really useful, because codes will continue to change
and linux has various platforms, kernel version, CPU, even derivations
with some extensions. Can one quarification cover all of them?
I feel it's good to just confirm core functionarities (l2cap, sdp and
gap for me).

Regards,
Takashi

  parent reply	other threads:[~2003-03-05  4:35 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
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 [this message]
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=8765qysa6g.wl@maple.sm.sony.co.jp \
    --to=sasai@sm.sony.co.jp \
    --cc=Halam.Rose@7layers-UK.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=david.libault@inventel.fr \
    --cc=dvpub@telus.net \
    --cc=marcel@rvs.uni-bielefeld.de \
    --cc=maxk@qualcomm.com \
    /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