public inbox for linux-bluetooth@vger.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] is SDPd required for RFCOMM calls ?
Date: Mon, 26 Nov 2007 07:27:11 +0100	[thread overview]
Message-ID: <1196058431.4217.83.camel@aeonflux> (raw)
In-Reply-To: <37666aa80711191548g5a63577ge13d215410c69fd0@mail.gmail.com>

Hi Han,

> I just started to use BlueZ to write bluetooth programs in C.  And I
> am using VMware based Ubuntu Linux.
> 
> I can do hci_inquiry successfully. But  when I tried to run a RFCOMM
> server program ( listen on channel 1).  The client always reports
> error : "Operation now in progress".
> 
> The same client can connect with no problem if i closed VMware +
> ubuntu and enable bluetooth in windows XP.
> 
> since the windows XP enables bluetooth & SDP services (Serial Port on
> RFCOMM channel 1),  i was wondering if SDP is required to do RFCOMM
> communication (on server side)  ?
> 
> or, is there anything else the server side need to do to accept the
> RFCOMM connections ?

start hcid -s and you get your SDP server.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-11-26  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 23:48 [Bluez-devel] is SDPd required for RFCOMM calls ? Han
2007-11-26  6:27 ` 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=1196058431.4217.83.camel@aeonflux \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox