public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Alok <develnewbie@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Help regarding TI's Bluetooth chips.
Date: Thu, 16 Aug 2007 19:07:13 +0530	[thread overview]
Message-ID: <1187271433.6440.18.camel@greatbear> (raw)

Hi, 

I am working on bluetooth on OMAP 850(fsample) board.
The Bluetooth chip is BRF6150 2.12 FW 3.0.48.
The Host Control Interface used is UART.
I came across this post:
http://sourceforge.net/mailarchive/message.php?msg_id=200704301139.44842.ohad%40bencohen.org 

I need to send a .bts to the BT chip for initialization. 
I am using the following patch for it: 
 http://article.gmane.org/gmane.linux.bluez.devel/5168

I want to get a2dp up on this chip. 

I had the following queries: 

1. Is HCILL critical for TI's BT chips? 

2. Has anyone tried a2dp on the brf63xx/brf61xx ? If so what is the
minimum baud rate that is required ? 

3. I have currently selected the H4 driver. Do i need to select the bcsp
driver instead? What is the difference betweent the two?


Thanks, 
Alok.


-------------------------------------------------------------------------
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

             reply	other threads:[~2007-08-16 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 13:37 Alok [this message]
2007-08-16 16:23 ` [Bluez-devel] Help regarding TI's Bluetooth chips Ohad Ben-Cohen

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=1187271433.6440.18.camel@greatbear \
    --to=develnewbie@gmail.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