Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Vinod Rayapudi <vinod.rayapudi@tcs.com>
Cc: linux-bluetooth@vger.kernel.org,
	linux-bluetooth-owner@vger.kernel.org,
	autoanswer@vger.kernel.org
Subject: Re: SPP profile in Bluez
Date: Mon, 9 Jun 2014 12:49:52 +0300	[thread overview]
Message-ID: <20140609094952.GA23710@t440s.lan> (raw)
In-Reply-To: <OF3D8FCC47.DCEA4A21-ON65257CF2.00332791-65257CF2.00332795@tcs.com>

Hi Vinod,

On Mon, Jun 09, 2014, Vinod Rayapudi wrote:
> I want to use SPP in Bluez stack.
> 
> Can anyone help me, from which versions of Bluez SPP is available ?

SPP has always been available with BlueZ. The only thing that has kept
changing a bit is the preferred way to implement it. The RFCOMM socket
interface would be an option that's available regardless of BlueZ
version, however it may not be the most convenient one if you can
restrict yourself to newer BlueZ versions.

> I would like to use SPP Connect, Disconnect, Read and Write functionalities.

With BlueZ 5 the simplest way is probably to use the Profile interface
(see doc/profile-api.txt and test/test-profile). If you implement that
interface you will get the new SPP connection (RFCOMM socket) handed
over to you over D-Bus once successfully connected. Connecting as client
would happen by issuing a ConnectProfile("spp") D-Bus method call.

Johan

  reply	other threads:[~2014-06-09  9:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09  9:18 SPP profile in Bluez Vinod Rayapudi
2014-06-09  9:49 ` Johan Hedberg [this message]
2014-06-09 12:55   ` Vinod Rayapudi
2014-06-09 13:56     ` Johan Hedberg
2014-06-12 12:06       ` Vinod Rayapudi
     [not found]     ` <OFBA204D5E.072B210A-ON65257CF5.004A997E-65257CF5.004A9980@LocalDomain>
2014-06-12 13:36       ` Vinod Rayapudi

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=20140609094952.GA23710@t440s.lan \
    --to=johan.hedberg@gmail.com \
    --cc=autoanswer@vger.kernel.org \
    --cc=linux-bluetooth-owner@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vinod.rayapudi@tcs.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