From: Mayank BATRA <mayank.batra@st.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluetooth 2.0
Date: Tue, 02 Jan 2007 09:17:07 +0530 [thread overview]
Message-ID: <4599D5BB.4070601@st.com> (raw)
In-Reply-To: <4595380D.3050004@xmission.com>
Hi,
Brad Midgley wrote:
>> I'm wondering if I could help the linux bluetooth subsystem by writing
>> code for the new Bluetooth 2.0 Spec. So, is there any project taking
>> care of this? Is there any activity for this?
>
> There are some profiles that aren't implemented but 2.0 is mostly
> covered. The esco transport isn't done fwiw--it was introduced back in 1.2.
Don't think there are any new profiles as such.
The only difference between 1.2 and 2.0 is EDR.
> Marcel has been working on features that will be in "Lisbon" (2.1?) like
> simple pairing and extended inquiry.
Marcel, I was going through the 2.1 spec and was interested in working
on features such as Extended Inquiry, Simple Pairing, Sniff Subrating etc.
Any starters?
Best Regards,
Mayank
---
Random Quote Follows:
All programmers want arrays!
* TagZilla 0.066 * http://tagzilla.mozdev.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-02 3:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 12:15 [Bluez-devel] Bluetooth 2.0 Felipe Balbi
2006-12-29 15:45 ` Brad Midgley
2007-01-02 3:47 ` Mayank BATRA [this message]
2007-01-02 3:58 ` Marcel Holtmann
2007-01-02 4:16 ` Mayank BATRA
2007-01-02 12:35 ` Felipe Balbi
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=4599D5BB.4070601@st.com \
--to=mayank.batra@st.com \
--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