public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [Bluez-devel] New BQB
@ 2004-04-08 14:49 Halam Rose
  2004-04-09 11:44 ` [Bluez-devel] rfcomm Problem amine
  2004-04-09 11:49 ` [Bluez-devel] Rfcomm problem amine
  0 siblings, 2 replies; 7+ messages in thread
From: Halam Rose @ 2004-04-08 14:49 UTC (permalink / raw)
  To: bluez-devel

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

Hello All,
 
I'm a BQB (Bluetooth Qualification Body) now so if anyone needs some
BlueZ friendly advice on Bluetooth Qualification and licensing drop me a
line.
 
A Bluetooth Qualification Body (BQB) is a person authorized by the BQRB
to provide services to a Member seeking Bluetooth product qualification.
Members contract directly with a BQB for qualification services. A BQB
is responsible for checking declarations and documents against
requirements, reviewing product test reports, and listing products on
the official database of Bluetooth qualified products.  The BQB is an
individual, and is not necessarily affiliated with a test facility or a
product manufacturer. 

The role and duties of a BQB are described in the Bluetooth
Qualification Program Reference Document (PRD), especially in section
4.3.4. 

Halam
 
 


Halam Rose
Bluetooth Qualification Body
Tel: +44 (0)1763 262524
Fax: +44 (0)1763 261177 

Halam.Rose@7layers-uk.com
http://www.7layers-uk.com



--------------------------------------------------------------------------------------------------------------------------------------------------
This communication is from 7 Layers UK Ltd., Melbourn Science Park, Cambridge Road, Melbourn, Hertfordshire SG8 6HB, England.
This email (including any attachments) is intended only for bluez-devel@lists.sourceforge.net. It may contain confidential or privileged
information. If you are not the intended recipient, please do not read, distribute, copy or otherwise use this communication or
the information in it. Any views or opinions expressed in this email may be solely those of the author and are not necessarily
those of 7 Layers UK Ltd. WARNING: Although 7 Layers UK Ltd have taken all reasonable precautions to ensure that viruses
are not present in this email, the company can accept no responsibility for any loss of data arising from the use of this email
or its attachments. If you have received this communication in error, please notify us by email (postmaster@7layers-UK.com)
or by telephone +44 (0) 1763 262524 and then delete the email and any copies of it.
--------------------------------------------------------------------------------------------------------------------------------------------------


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

^ permalink raw reply	[flat|nested] 7+ messages in thread
* [Bluez-devel] RFCOMM problem
@ 2004-04-01 23:12 zubiwat
  0 siblings, 0 replies; 7+ messages in thread
From: zubiwat @ 2004-04-01 23:12 UTC (permalink / raw)
  To: devel Bluetooth

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

Hi 
I'm connected through L2CAP and what should I send now to connect RFCOMM. I know that it should be SABM and I should wait for UA but how to do this?
Where is a command to do this and how it looks like. RFCOMM packets are insight L2CAP as a command?
Can anyone tell me what it's like and howto make a command to send SABM and make rfcomm connection?

Regards 

Maciej

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2004-04-09 16:09 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-04-08 14:49 [Bluez-devel] New BQB Halam Rose
2004-04-09 11:44 ` [Bluez-devel] rfcomm Problem amine
2004-04-09 11:49 ` [Bluez-devel] Rfcomm problem amine
2004-04-09 12:05   ` Marcel Holtmann
2004-04-09 12:32     ` amine
2004-04-09 16:09       ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2004-04-01 23:12 [Bluez-devel] RFCOMM problem zubiwat

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox