From: "Ohad Ben-Cohen" <ohad@bencohen.org>
To: Alok <develnewbie@gmail.com>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Help regarding TI's Bluetooth chips.
Date: Thu, 16 Aug 2007 19:23:27 +0300 [thread overview]
Message-ID: <bd5b16740708160923g17faaaecj77d3f9abd517a65a@mail.gmail.com> (raw)
In-Reply-To: <1187271433.6440.18.camel@greatbear>
Hi Alok,
On 8/16/07, Alok <develnewbie@gmail.com> wrote:
> 1. Is HCILL critical for TI's BT chips?
No. HCILL is TI's runtime power management protocol. It is not mandatory;
In fact it is off by default and a special command must be sent to the chip
in order to turn it on (usually it is the last command in the .bts file).
We are currently working on merging the HCILL patches to mainline.
If you are interested, take a look at:
http://article.gmane.org/gmane.linux.bluez.devel/12071
> 2. Has anyone tried a2dp on the brf63xx/brf61xx ? If so what is the
> minimum baud rate that is required ?
A safe minimum value would be 460kbps (although there are some bitpool values
that will make even a baud rate of ~200-300kbps enough).
> 3. I have currently selected the H4 driver. Do i need to select the bcsp driver instead?
HCILL is just an extension of H4 (a few single-byte commands with which the chip
can announce its power state, and the host can wake it up).
When HCILL is off, the BRF chips speak plain H4, so If you don't want HCILL,
you should indeed use H4.
The BCSP is a communication protocol required for CSR BlueCore chips.
Don't use it.
All the best,
Ohad.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-08-16 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 13:37 [Bluez-devel] Help regarding TI's Bluetooth chips Alok
2007-08-16 16:23 ` Ohad Ben-Cohen [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=bd5b16740708160923g17faaaecj77d3f9abd517a65a@mail.gmail.com \
--to=ohad@bencohen.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=develnewbie@gmail.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