linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] csr + edr + class 1 *finally* in US
Date: Fri, 10 Feb 2006 01:55:23 +0100	[thread overview]
Message-ID: <1139532923.17280.33.camel@localhost> (raw)
In-Reply-To: <43EBCB5D.7070300@xmission.com>

Hi Brad,

> We've had to wait long enough I suppose. Now these can be purchased
> finally. It's in the Bluetake bt007ex:
> 
> http://www.btboutique.com/product_info.php?products_id=176
> 
> It also comes with windows & mac drivers so I'm going to try to use it
> to get avrcp fully figured out... (is there a way in macos to spy on usb?)
> 
> jag:/home/bmidgley# hciconfig hci1 revision
> hci1:   Type: USB
>         BD Address: 50:00:20:F4:00:6F ACL MTU: 384:8 SCO MTU: 64:8
>         HCI 19.2
>         Chip version: BlueCore4-ROM
>         Max key size: 128 bit
>         SCO mapping:  HCI

cool, the first one with really 128 bit encryption. You can also call
"bccmd buildname" to get the full build name.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2006-02-10  0:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09 23:08 [Bluez-devel] csr + edr + class 1 *finally* in US Brad Midgley
2006-02-10  0:55 ` Marcel Holtmann [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=1139532923.17280.33.camel@localhost \
    --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;
as well as URLs for NNTP newsgroup(s).