linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Mischke <survivor@uni-paderborn.de>
To: "Antony C. Roberts" <acr@acroberts.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] RE: Accessing HCI on Windows
Date: Wed, 24 Mar 2004 00:19:36 +0100	[thread overview]
Message-ID: <4060C608.6070206@uni-paderborn.de> (raw)
In-Reply-To: <20040323183316.0D30C5EE02E@pfepb.post.tele.dk>

Thanks! This is exactly what I was looking for. I've tested it and ist 
works.
I've seen FreeBT before (in January), but at that time they had no 
working USB support.
As for me, this thread is closed.
Again: Thanks to all contributors!

Kind regards
Stefan

Antony C. Roberts schrieb:

>Check out FreeBT (www.freebt.net) it's open source and includes the full
>source code to a Generic Windows Bluetooth USB Driver as well as various
>levels of HCI abstraction (with full access to the HCI layer) in C++.
>
>Regards,
>Antony C. Roberts.
>
>  
>
>  
>


-------------------------------------------------------
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

      reply	other threads:[~2004-03-23 23:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040323173139.19B991D01C5@sc8-sf-uberspam1.sourceforge.net>
2004-03-23 18:33 ` [Bluez-devel] RE: Accessing HCI on Windows Antony C. Roberts
2004-03-23 23:19   ` Stefan Mischke [this message]

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=4060C608.6070206@uni-paderborn.de \
    --to=survivor@uni-paderborn.de \
    --cc=acr@acroberts.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;
as well as URLs for NNTP newsgroup(s).