public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: amine@baracoda.com
To: "Halam Rose" <Halam.Rose@7layers-uk.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] rfcomm Problem
Date: Fri, 9 Apr 2004 13:44:10 +0200 (CEST)	[thread overview]
Message-ID: <33072.82.127.5.232.1081511050.squirrel@baracoda.com> (raw)
In-Reply-To: <C1B29E01A9B748458D51DBBE04E4B9EA2E5628@7layers.7layers-uk.com>

Hello All,

I have a probleme with rfcomm connection.
when i try to connect my bluetooth interface using rfcomm it working but i
have this message:
&Can't open RFCOMM device: No such file or directory


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



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-04-09 11:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 14:49 [Bluez-devel] New BQB Halam Rose
2004-04-09 11:44 ` amine [this message]
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

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=33072.82.127.5.232.1081511050.squirrel@baracoda.com \
    --to=amine@baracoda.com \
    --cc=Halam.Rose@7layers-uk.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox