From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] TI BTS for hciattach
Date: Sun, 19 Jun 2005 01:24:46 +0200 [thread overview]
Message-ID: <1119137087.9217.3.camel@pegasus> (raw)
In-Reply-To: <42B31512.8060301@sdgsystems.com>
Hi Todd,
> This proposed patch implements the TI BTS (Bluetooth script) mechanism.
> I have attached the diff and new files to be built along with hciattach.
> I have also attached a sample BTS file (the one that goes along with the
> BRF6150 plus firmware, as found in the iPAQ hx4700). The code is a bit
> chatty (prints BTS comment lines), but provides feedback as to what is
> being done with the chip. Comments / Suggestions welcome.
is it possible to get a development kit with the BRF6150 from TI? I like
to test this new code.
Do we get the full specification of BTS? I think we need to rewrite some
parts of the TI code. I don't like the coding style and parts of it look
too much like crappy Windows code.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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:[~2005-06-18 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 18:23 [Bluez-devel] [PATCH] TI BTS for hciattach Todd Blumer
2005-06-18 23:24 ` Marcel Holtmann [this message]
[not found] <20050619030502.89EF71243E@sc8-sf-spam2.sourceforge.net>
2005-06-19 12:18 ` Todd Blumer
2005-06-19 12:33 ` 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=1119137087.9217.3.camel@pegasus \
--to=marcel@holtmann.org \
--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.