From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] a2dp on iTech works
Date: Fri, 08 Apr 2005 00:10:34 +0200 [thread overview]
Message-ID: <1112911835.26175.2.camel@pegasus> (raw)
In-Reply-To: <4255ADED.3080200@xmission.com>
Hi Brad,
> here's the info
>
> BD Address: 00:0D:3C:30:04:0F
> Device Name: i.Tech stereo headset
> LMP Version: 1.2 (0x2) LMP Subversion: 0x703
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xff 0xff 0x8f 0xf8
>
> <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>
> <enhanced iscan>
> <interlaced iscan>
> <interlaced pscan>
> <inquiry with RSSI>
> <extended SCO>
> <AFH cap. slave>
> <AFH class. slave>
> <AFH cap. master>
> <AFH class. master>
> <extended features>
this looks weird and normally means that the bluez-libs and bluez-utils
are not matching. However this is the first CSR based headphone I've
seen so far.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-07 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 21:08 [Bluez-devel] a2dp on iTech works Brad Midgley
2005-04-07 21:16 ` Marcel Holtmann
2005-04-07 22:02 ` Brad Midgley
2005-04-07 22:10 ` Marcel Holtmann [this message]
2005-04-07 22:29 ` Brad Midgley
2005-04-07 22:30 ` Brad Midgley
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=1112911835.26175.2.camel@pegasus \
--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