From: "durai" <durai@isofttech.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] support for CSR Bluecore4 chip
Date: Sat, 2 Apr 2005 14:15:12 +0530 [thread overview]
Message-ID: <20050402141512.1882699599.durai@isofttech.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 170 bytes --]
Hi,
We are going to use Bluecore4 chip for our product. I wanted to know whether the current bluez implementation
will support Bluecore4 chipset.
thanks
durai
[-- Attachment #2: Type: text/html, Size: 1050 bytes --]
next reply other threads:[~2005-04-02 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 8:45 durai [this message]
2005-04-03 19:00 ` [Bluez-devel] support for CSR Bluecore4 chip Marcel Holtmann
2005-04-07 7:27 ` durai
2005-04-07 7:39 ` durai
2005-04-07 10:10 ` Marcel Holtmann
2005-04-07 10:08 ` Marcel Holtmann
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=20050402141512.1882699599.durai@isofttech.com \
--to=durai@isofttech.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