Linux bluetooth development
 help / color / mirror / Atom feed
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 14:33:44 +0200	[thread overview]
Message-ID: <1119184424.9217.15.camel@pegasus> (raw)
In-Reply-To: <42B56293.9060309@sdgsystems.com>

Hi Todd,

> I will check with TI about the possibility of getting you documentation and / or development kit. Maybe we can loan you an iPAQ hx4700.

please do so, but I like to use a real development kit instead of the
iPAQ. Setting up the cross-compile toolchain takes me longer then doing
it on my development system.

However, please post the output of "hciconfig -a" so I can add this
device to my device list.

Do you know about some specific TI commands to get more details about
the chip and its firmware? I like to add it to the revision command of
hciconfig.

> (Yes, the code did come from windows, and a re-write is fine. I didn't take the time at this point, since it was working.)

I must keep my eyes a little bit on the code quality ;)

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

  reply	other threads:[~2005-06-19 12:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050619030502.89EF71243E@sc8-sf-spam2.sourceforge.net>
2005-06-19 12:18 ` [Bluez-devel] [PATCH] TI BTS for hciattach Todd Blumer
2005-06-19 12:33   ` Marcel Holtmann [this message]
2005-06-17 18:23 Todd Blumer
2005-06-18 23:24 ` 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=1119184424.9217.15.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox