public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Shopping advice: bluetooth 2.0 USB dongle with CSR chipset?
Date: Mon, 26 Feb 2007 21:43:11 -0700	[thread overview]
Message-ID: <45E3B6DF.4000008@xmission.com> (raw)
In-Reply-To: <45E2A6D1.6020407@yahoo.com.au>

hey

> that it doesn't say "Chip version: BlueCore3-ROM".  And if you find a
> source of dongles that say "BlueCore4-External", please let the list know...

I've noticed these getting harder to find too.

fwiw the only -ext I have is the wt11-a-hci bluetooth module from
semiconductorstore.com. you still have to add a regulator and a usb
connector. It would be best if you could find someone integrating this
module or talk someone into laying it out for batchpcb.com

brad

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-02-27  4:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0702122031580.2496@cherokee.spacecom.si>
2007-02-14 12:10 ` [Bluez-users] Shopping advice: bluetooth 2.0 USB dongle with CSR chipset? bluez.mexon
2007-02-16  9:44   ` Anssi Saari
2007-02-16 10:56     ` bluez.mexon
2007-02-26  9:22       ` bluez.mexon
2007-02-27  4:43         ` Brad Midgley [this message]
2007-02-27 14:09           ` bluez.mexon
2007-02-12 10:20 bluez.mexon

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=45E3B6DF.4000008@xmission.com \
    --to=bmidgley@xmission.com \
    --cc=bluez-users@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