From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: class 1 bluetooth 1.2 dongles with CSR chipset?
Date: Wed, 05 Oct 2005 19:50:16 +0200 [thread overview]
Message-ID: <1128534616.5447.32.camel@localhost.localdomain> (raw)
In-Reply-To: <20051005152912.GA2686@intevation.de>
Hi Thomas,
> > try to get a Cellink BlueCore4 based dongle with EDR support.
>
> The two Cellink BTA6030 arrived today, here the output of
> hciconfig hci1 features version revision:
>
> hci1: Type: USB
> BD Address: 00:0A:94:xx:xx:xx ACL MTU: 384:8 SCO MTU: 64:8
> Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
> <3-slot packets> <5-slot packets> <encryption> <slot offset>
> <timing accuracy> <role switch> <hold mode> <sniff mode>
> <park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
> <power control> <transparent SCO> <broadcast encrypt>
> <EDR ACL 2 Mbps> <EDR ACL 3 Mbps> <enhanced iscan>
> <interlaced iscan> <interlaced pscan> <inquiry with RSSI>
> <extended SCO> <EV4 packets> <EV5 packets> <AFH cap. slave>
> <AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL>
> <AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps>
> <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended features>
> HCI Ver: 1.1 (0x1) HCI Rev: 0x5dc LMP Ver: 1.1 (0x1) LMP Subver: 0x5dc
> Manufacturer: Cambridge Silicon Radio (10)
> Build 1500
> Chip version: BlueCore4-External
> Max key size: 56 bit
> SCO mapping: HCI
>
> The version numbers look strange.
the version numbers can be corrected with the pskey tool. Check version
and remver PS keys.
> Unfortunately the dongles only support 56bit encryption.
You can flash a 128-bit firmware into it, but currently no such firmware
is not available in the public.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-10-05 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 12:41 [Bluez-users] class 1 bluetooth 1.2 dongles with CSR chipset? Thomas Arendsen Hein
2005-09-30 13:33 ` Marcel Holtmann
2005-09-30 16:59 ` [Bluez-users] " Thomas Arendsen Hein
2005-10-01 9:12 ` Marcel Holtmann
2005-10-05 15:29 ` Thomas Arendsen Hein
2005-10-05 17:50 ` Marcel Holtmann [this message]
2005-09-30 22:16 ` [Bluez-users] " Christian Schuglitsch
2005-10-13 21:24 ` Christian Schuglitsch
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=1128534616.5447.32.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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;
as well as URLs for NNTP newsgroup(s).