From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] First dongle with EDR support
Date: Wed, 08 Jun 2005 05:18:33 +0200 [thread overview]
Message-ID: <1118200713.10148.3.camel@notepaq> (raw)
In-Reply-To: <5256d0b0506070651237c7503@mail.gmail.com>
Hi Pete,
> > it seems that Cellink is building the first EDR dongle. It is qualified
> > and you will find it on their website.
> >
> > http://www.cellink.com.tw/pro-bta-6030.htm
>
> Well I ordered one of these yesterday, it arrivied today. I plugged it
> in and away it went :-) It seems to work OK but I don't have time at
> the moment to test it out properly but doing a 'sdptool browse' finds
> my phone.
>
> Some details:
>
> [root@localhost ~]# hciconfig -a
> hci0: Type: USB
> BD Address: 00:0A:94:01:8A:3A ACL MTU: 384:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:107 acl:0 sco:0 events:14 errors:0
> TX bytes:300 acl:0 sco:0 commands:13 errors:0
> Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'localhost.localdomain-0'
> Class: 0x120104
> Service Classes: Networking
> Device Class: Computer, Desktop workstation
> HCI Ver: 1.1 (0x1) HCI Rev: 0x5dc LMP Ver: 1.1 (0x1) LMP Subver: 0x5dc
> Manufacturer: Cambridge Silicon Radio (10)
this is strange. The feature bits say that it supports EDR, but the
Bluetooth version still shows 1.1.
Please do a "hciconfig hci0 version features revision" as root with the
latest bluez-utils version. I am also interersted what lsusb shows you
and what is the content of /proc/bus/usb/devices.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-06-08 3:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 8:55 [Bluez-devel] First dongle with EDR support Marcel Holtmann
2005-06-03 9:37 ` Peter Robinson
2005-06-03 9:50 ` Marcel Holtmann
2005-06-03 10:01 ` Peter Robinson
2005-06-03 13:46 ` Mitja Pufic
2005-06-07 13:51 ` Peter Robinson
2005-06-08 3:18 ` Marcel Holtmann [this message]
2005-06-08 7:11 ` Peter Robinson
2005-06-12 9:18 ` Matthias Thomae
-- strict thread matches above, loose matches on Subject: below --
2005-06-03 9:28 Victor Shcherbatyuk
2005-06-03 9:46 ` Marcel Holtmann
2005-06-03 10:16 Victor Shcherbatyuk
2005-06-03 10:31 ` Peter Robinson
2005-06-03 11:32 ` Marcel Holtmann
2005-06-08 8:21 Victor Shcherbatyuk
2005-06-08 8:30 ` Peter Robinson
2005-06-08 8:38 ` 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=1118200713.10148.3.camel@notepaq \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.