From: pramod gurav <pramod_gurav_etc@yahoo.co.in>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Add support for Texas Instruments' chips
Date: Fri, 11 Jul 2008 11:42:49 +0530 (IST) [thread overview]
Message-ID: <693063.42845.qm@web8402.mail.in.yahoo.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1628 bytes --]
Hi Ohad
Sorry to break the link.
I am working on arm platform. I want to configure TI's brf6350 on UART.
I read some of the mail on the list. I came to know that hci_ll.c provides support for brf6350.
Is the hci lower level support in kernel enough to drive the chip?
What else I have to do at kernel side to bring UP my brf6350?
Where would I get the brf script file for my chip?
Your response is much awaited.
Thanks and Best regards
Pramod
----- Original Message ----
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Sent: Thursday, 10 July, 2008 6:03:23 PM
Subject: Re: [Bluez-devel] [PATCH] Add support for Texas Instruments' chips
Hi Ohad,
> > please put all the TI code into hciattach_ti.c and then I gonna apply
> > this patch.
>
> I'm gonna have to put some common definitions in hciattach.h then
> (mainly struct uart_t).
>
> Is that ok ?
no. Do the same as I did for hciattach_st.c
Regards
Marcel
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Explore your hobbies and interests. Go to http://in.promos.yahoo.com/groups/
[-- Attachment #1.2: Type: text/html, Size: 2526 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2008-07-11 6:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 6:12 pramod gurav [this message]
2008-07-11 8:43 ` [Bluez-devel] [PATCH] Add support for Texas Instruments' chips Ohad Ben-Cohen
-- strict thread matches above, loose matches on Subject: below --
2008-07-03 10:02 Ben-cohen, Ohad
2008-07-10 4:07 ` Marcel Holtmann
2008-07-10 5:36 ` Ohad Ben-Cohen
2008-07-10 12:33 ` Marcel Holtmann
2008-07-11 6:14 ` Marcel Holtmann
2008-07-11 8:21 ` Ben-cohen, Ohad
2008-07-11 8:37 ` Marcel Holtmann
2008-07-11 8:38 ` Ohad Ben-Cohen
2008-07-11 8:50 ` Marcel Holtmann
2008-07-11 8:52 ` 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=693063.42845.qm@web8402.mail.in.yahoo.com \
--to=pramod_gurav_etc@yahoo.co.in \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.