From: Szymon Janc <szymon.janc@gmail.com>
To: Jim Hollister <jim.hollister@allure-energy.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Need advice: bluez on older Linux kernel?
Date: Wed, 02 Apr 2014 18:27:25 +0200 [thread overview]
Message-ID: <4703706.SxBd8VXgKP@athlon> (raw)
In-Reply-To: <CF61A08A.5BFD%jim.hollister@allure-energy.com>
Hi Jim,
On Wednesday 02 April 2014 11:10:02 Jim Hollister wrote:
> I need to add Bluetooth Low Energy (BLE) capability to an ARM-based embedded
> system that's currently based on Ubuntu Lucid 11.04 and Linux kernel
> 2.6.35. I've read that BLE support in bluez requires Linux kernel version
> 3.5 or later. At this point, I think this leaves me with four options:
>
> A) Upgrade the embedded system to a recent Linux kernel >= 3.5
> B) Backport the most recent bluez to run on Linux kernel 2.6.35
> C) Combine both approaches A and C, so that the embedded system and bluez
> meet at a kernel version somewhere between 2.6.35 and 3.5
> D) Find a different BLE stack that will run on Linux kernel 2.6.35. I see a
> number of those described at
> http://en.wikipedia.org/wiki/Bluetooth_stack#Embedded_implementations
>
> I would much prefer to use bluez, but I'm concerned about the effort
> involved in upgrading the embedded system, and I don't know anything about
> the feasibility of backporting bluez. Would some kind and knowledgeable
> person please give me some advice or an opinion about how I should approach
> this?
I suggest using backports project [1] to update Linux Bluetooth subsystem in
kernel. Also best would be to use latest available release.
[1] http://backports.wiki.kernel.org
--
Szymon K. Janc
szymon.janc@gmail.com
prev parent reply other threads:[~2014-04-02 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 16:10 Need advice: bluez on older Linux kernel? Jim Hollister
2014-04-02 16:27 ` Szymon Janc [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=4703706.SxBd8VXgKP@athlon \
--to=szymon.janc@gmail.com \
--cc=jim.hollister@allure-energy.com \
--cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).