From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] TPL (transmit power level)
Date: Tue, 22 Feb 2005 04:16:34 +0100 [thread overview]
Message-ID: <1109042195.7626.105.camel@pegasus> (raw)
In-Reply-To: <de33c8be05022119091917b7ff@mail.gmail.com>
Hi Flavio,
> My dongle is an conceptronic CBT100U class1 (100m) and here it=B4s the
> information :
>=20
> chip version : BlueCore2 ;
> HCI 17,11 ;
>=20
> SCO mapping : HCI ;
> HCI ver:1,1 ;
> HCI rev: 0X460;
> LMP ver:1,1 ;
> LMP subver:0X460
> Should i update the firmware? Resolves my problem?In the chip specific
> don=B4t say about the class 1 :(
the class stuff is also not chip specific. The antenna matters in this
case.
> Note: My dongle is 1,1 version but can i update for the 1,2 version
> with the firmware?
Maybe yes, maybe no. What does /proc/bus/usb/devices contain?
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-02-22 3:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 12:25 [Bluez-devel] TPL (transmit power level) Flávio
2005-02-21 23:24 ` Marcel Holtmann
2005-02-22 2:16 ` Flávio
2005-02-22 2:28 ` Marcel Holtmann
2005-02-22 3:09 ` Flávio
2005-02-22 3:16 ` Marcel Holtmann [this message]
2005-02-22 14:43 ` Flávio
2005-02-22 15:08 ` Marcel Holtmann
2005-02-22 15:20 ` Flávio
2005-02-22 16:59 ` Steven Singer
2005-02-22 19:20 ` Flávio
2005-02-23 14:43 ` Steven Singer
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=1109042195.7626.105.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