From: Marcel Holtmann <marcel@holtmann.org>
To: Steven Singer <steven.singer@csr.com>
Cc: paolo2278@freemail.it,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] absolute clock
Date: Wed, 31 Mar 2004 14:14:26 +0200 [thread overview]
Message-ID: <1080735266.2674.88.camel@pegasus> (raw)
In-Reply-To: <406AB277.2030503@csr.com>
Hi Steven,
> If you have access to the CSR support website (www.csrsupport.com) then
> it's all fully documented. Don't forget that you may need to tunnel the
> commands over HCI. Alternatively, you might find it easier to dig through
> the BlueZ source and find out where it sends the commands to change the
> uart baud rate - that should give you a good example to work from.
the better example code will be in utils/tools/csr.[ch].
> I can't recall if BlueZ has a tool that allows you to send arbitrary
> BCCMDs to CSR chips - if not, it sounds like a good project for
> someone.
A program like btcli don't exists for Linux.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-03-31 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 10:46 [Bluez-devel] absolute clock paolo2278
2004-03-31 10:56 ` Marcel Holtmann
2004-03-31 11:58 ` Steven Singer
2004-03-31 12:14 ` Marcel Holtmann [this message]
[not found] <20040331113603.3852.qmail@mail.supereva.it>
2004-03-31 11:41 ` 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=1080735266.2674.88.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=paolo2278@freemail.it \
--cc=steven.singer@csr.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