Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Ssagarr Patil <hugarsagar@outlook.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: bluez5 pairing devices
Date: Tue, 17 Mar 2015 19:41:43 +0100	[thread overview]
Message-ID: <12627750.IG3ACNRtuD@leonov> (raw)
In-Reply-To: <46068BD2-CF33-4617-80DB-5AE5C1FCA364@holtmann.org>

Hi,

On Tuesday 17 of March 2015 09:42:44 Marcel Holtmann wrote:
> Hi Sagar,
> 
> >>>>> I am very new to bluetooth, so sorry for a novice query.
> >>>>> 
> >>>>> 1: I am using 2.6.37 Linux kernel, can bluez5 stack be used on this or
> >>>>> should I use bluez4 ? 2: With bluez5 I am able to scan devices and
> >>>>> also see the device on other device but I am not able to pair them Is
> >>>>> there some sort of deamon required to pair them ?
> >>>> 
> >>>> BlueZ 5 requires a Bluetooth subsystem with management API support. So
> >>>> at least kernel 3.4 or you have to use Linux backports to at least
> >>>> bring the Bluetooth subsystem to your 2.6.37 kernel. And I have heard
> >>>> of success from people doing that, but I have not personally done
> >>>> that.>>> 
> >>> Probably that would take me more time in back porting. In case of 2.6.37
> >>> what version of bluez4 would be best ?>> 
> >> the Linux backports project does that automatically. Give it a try. You
> >> are not the person with this problem, but it is not something were BlueZ
> >> upstream will be of much assistance.> 
> > Any quick pointers on doing this ?
> 
> https://backports.wiki.kernel.org/
> 
> >> I think that our android/README has even some instructions on how to get
> >> that started for an Android build. You might be able to adapt that
> >> quickly.> 
> > I am more interested in Linux.
> 
> It is still running the same Linux kernel. That is why I said, you might be
> able to adapt that to your needs.

Just an note that recent backports dropped support for kernels older than 3.0.
So some older release might be needed for 2.6.37.

-- 
BR
Szymon Janc

  reply	other threads:[~2015-03-17 18:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 10:48 bluez5 pairing devices Ssagarr Patil
     [not found] ` <,<46068BD2-CF33-4617-80DB-5AE5C1FCA364@holtmann.org>
     [not found]   ` <,<,<12627750.IG3ACNRtuD@leonov>
     [not found]     ` <,<BAY176-W40E12E1C2F620AB0D38605D3000@phx.gbl>
     [not found]       ` <,<440EB08C-2BD4-4373-B3DC-80361AA74722@holtmann.org>
2015-03-17 15:08 ` Marcel Holtmann
2015-03-17 16:05   ` Ssagarr Patil
2015-03-17 16:10     ` Marcel Holtmann
2015-03-17 16:32       ` Ssagarr Patil
2015-03-17 16:42         ` Marcel Holtmann
2015-03-17 18:41           ` Szymon Janc [this message]
2015-03-18 12:09             ` Ssagarr Patil
2015-03-18 16:28               ` Marcel Holtmann
2015-03-19 12:23                 ` Ssagarr Patil
2015-03-19 12:56                   ` Ssagarr Patil
2015-03-19 14:08                     ` Marcel Holtmann
2015-03-19 15:13                       ` Ssagarr Patil
2015-03-19 16:02                         ` Marcel Holtmann
2015-03-19 20:00                           ` Ssagarr Patil
2015-03-20 10:06                             ` Ssagarr Patil
2015-03-22  9:37                               ` Ssagarr Patil

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=12627750.IG3ACNRtuD@leonov \
    --to=szymon.janc@tieto.com \
    --cc=hugarsagar@outlook.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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