From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] "comlicated" setup - known issues for hid and SCO?
Date: Mon, 09 Aug 2004 19:25:10 +0200 [thread overview]
Message-ID: <4117B376.3030507@dark-reality.de> (raw)
In-Reply-To: <1092071597.4564.17.camel@pegasus>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marcel Holtmann wrote:
| Hi Lars,
|
|
|>right now I'm using two BT devices with my Epox dongle, an MX900 mice
|>and a Sony Ericcson HBH-35 Headset with snd-bt-sco (voice mode 0x0060,
|>before you ask ;)
|
|
| what does "hcitool info ..." say about your headset? What is the
| firmware version of your EPoX dongle?
|
|
Headset:
~ BD Address: 00:0E:07:33:DE:2B
~ Device Name: HBH-35
~ LMP Version: 1.1 (0x1) LMP Subversion: 0x8d40
~ Manufacturer: Ericsson Technology Licensing (0)
~ Features: 0xbc 0x28 0x01 0x00 0x00 0x00 0x00 0x00
~ <encryption> <slot offset> <timing accuracy> <role switch>
~ <sniff mode> <SCO link> <HV3 packets> <CVSD>
Mouse:
~ BD Address: 00:07:61:04:D6:7D
~ Device Name: Logitech MX900 Mouse
~ LMP Version: 1.1 (0x1) LMP Subversion: 0x350
~ Manufacturer: Cambridge Silicon Radio (10)
~ Features: 0xfc 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
~ <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>
How can I find out what firmware my dongle has? It's a BT-DG03...
cu,
~ Lars
PS: great mouse, by the way. Works perfectly with Bluetooth and connects
easily to different systems.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBF7N2QWC6DTWkDAoRArpEAJ4mMDV59gdZUyPBzsZ3a+iqrZsBtwCfZPPZ
TJWAeT+qMUXQ3nGs7DxbrYA=
=gvqb
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-08-09 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 16:40 [Bluez-devel] "comlicated" setup - known issues for hid and SCO? Lars Grunewaldt
2004-08-09 17:13 ` Marcel Holtmann
2004-08-09 17:25 ` Lars Grunewaldt [this message]
2004-08-09 17:44 ` Marcel Holtmann
[not found] ` <4117BA71.5000800@dark-reality.de>
2004-08-09 22:29 ` Marcel Holtmann
2004-08-10 0:03 ` Lars Grunewaldt
2004-08-10 12:51 ` Marcel Holtmann
2004-08-10 12:25 ` Lars Grunewaldt
2004-08-10 12:49 ` 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=4117B376.3030507@dark-reality.de \
--to=lgw@dark-reality.de \
--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