From: "Brian Gix" <bgix@codeaurora.org>
To: "'Vinicius Costa Gomes'" <vinicius.gomes@openbossa.org>,
"'Gustavo F. Padovan'" <padovan@profusion.mobi>,
"'Ville Tervo'" <ville.tervo@nokia.com>
Cc: <linux-bluetooth@vger.kernel.org>
Subject: RE: LE Kernel (bluetooth-le-2.6) and LE Security Manager
Date: Fri, 3 Dec 2010 16:40:13 -0800 [thread overview]
Message-ID: <001f01cb934b$d065e4c0$7131ae40$@org> (raw)
In-Reply-To: <20101203220534.GA16709@eris>
Hi Vinicius & Gustavo,
-----Original Message-----
From: Vinicius Costa Gomes [mailto:vinicius.gomes@openbossa.org]
Sent: 03 December, 2010 2:06 PM
To: Brian Gix
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: LE Kernel (bluetooth-le-2.6) and LE Security Manager
Hi Brian,
On 11:11 Fri 03 Dec, Brian Gix wrote:
>
> Hi Claudio, Johan & All,
>
> Is this LE capable kernel that Ville is working on, the development stream
> for the LE Security Manager? And if so, is it in a partial fleshed out
> state?
There is a simple implementation of SMP here[1] on my "devel" branch. I am
cleaning it up for sending it for review.
If you want to help, have any comments or just want to tell us what you are
working on, please drop by #bluez on freenode, or send an email.
[Gix] Unfortunately, I can't access git.infradead.org. Gustavo, would it be
possible for you to pull Vinicius' devel branch from
git://git.infradead.org/users/vcgomes/linux-2.6.git to an le-devel branch on
your bluetooth-testing repository?
[Gix] I am trying to integrate Qualcomm's latest LE capable (BR/EDR/LE)
chipset with bluez. Additionally, I do have a working non-open-source
[Gix] host which has had it's LE Security Manager UPF tested, which I hope
to be able to use to help test/solidify the bluez version.
>
> >
git://git.kernel.org/pub/scm/linux/kernel/git/vtervo/bluetooth-le-2.6.git
>
>
> Brian Gix
> bgix@codeaurora.org
> Employee of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Cheers,
--
Vinicius
[1] git://git.infradead.org/users/vcgomes/linux-2.6.git
next prev parent reply other threads:[~2010-12-04 0:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 19:11 LE Kernel (bluetooth-le-2.6) and LE Security Manager Brian Gix
2010-12-03 22:05 ` Vinicius Costa Gomes
2010-12-04 0:40 ` Brian Gix [this message]
2010-12-06 14:50 ` Vinicius Costa Gomes
2011-01-24 19:03 ` Brian Gix
2011-01-24 20:09 ` Luiz Augusto von Dentz
2011-01-24 20:33 ` Brian Gix
2011-01-24 21:34 ` Vinicius Costa Gomes
2011-01-25 8:35 ` Luiz Augusto von Dentz
2011-01-25 16:58 ` Brian Gix
2011-01-25 17:10 ` Brian Gix
2011-01-25 17:59 ` Johan Hedberg
2011-01-25 18:35 ` Brian Gix
2011-01-25 21:44 ` Luiz Augusto von Dentz
2011-01-25 22:04 ` Brian Gix
2011-01-26 17:54 ` Brian Gix
2011-01-28 23:19 ` GATT and D-Bus Inga Stotland
2011-01-29 0:07 ` Vinicius Costa Gomes
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='001f01cb934b$d065e4c0$7131ae40$@org' \
--to=bgix@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
--cc=ville.tervo@nokia.com \
--cc=vinicius.gomes@openbossa.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).