From: Marcel Holtmann <marcel@holtmann.org>
To: grpmind+bluez.users@boromir.vpop.net
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] How to configure a 723kbps connection?
Date: Tue, 17 Feb 2004 16:37:23 +0100 [thread overview]
Message-ID: <1077032243.2665.7.camel@pegasus> (raw)
In-Reply-To: <20040217132821.A599132D2F@mail.rvs.uni-bielefeld.de>
Hi Matt,
> > please run "hcitool info <bdaddr>" to show us what kind of Bluetooth
> > chip is inside. I think it is a Zeevo one.
>
> $ hcitool info 00:04:3E:81:90:E0
> Requesting information ...
> BD Address: 00:04:3E:81:90:E0
> Device Name: Pocket_PC
> LMP Version: 1.1 (0x1) LMP Subversion: 0x8d
> Manufacturer: Telencomm Inc. (18)
> Features: 0xff 0xff 0x05 0x00 0x00 0x00 0x00 0x00
> <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> <power control>
>
> The folks at handhelds.org think it's a Zeevo:
> http://www.handhelds.org/platforms/hp/ipaq-h22xx/tc2k_public.pdf
it is a Zeevo chip, but it is the old generation and I had not very good
experiences with it.
> > It can happen, because some link managers only does this right when they
> > are connected to there own dongles.
>
> Do you know which dongles have bad link managers?
It is not the dongle itself. It is the firmware inside and it is a
problem of both sides. It is safe to fallback to DM1, but this means
that the bandwith will be decreased. If you have chips from the same
manufacturer on both sides everything is almost fine. Personally I
prefer CSR chips, because they cause less troubles. But to decide which
side is doing bad on the link manager, you must use a protocol analyser.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-02-17 15:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 6:36 [Bluez-users] How to configure a 723kbps connection? grpmind+bluez.users
2004-02-17 15:37 ` Marcel Holtmann [this message]
[not found] <lists.bluez.users.1077061006.2665.141.camel@pegasus.SOMEWHERE>
[not found] ` <lists.bluez.users.4032E137.7080902@vpop.net>
2004-02-18 3:56 ` Matthew Reimer
[not found] <lists.bluez.users.1077037423.2665.72.camel@pegasus.SOMEWHERE>
[not found] ` <lists.bluez.users.403291AD.7080601@csr.com>
2004-02-17 23:09 ` Matthew Reimer
2004-02-17 23:36 ` Marcel Holtmann
2004-02-18 3:51 ` Matthew Reimer
2004-02-24 3:49 ` Matthew Reimer
2004-02-25 15:03 ` Paulo Marques
[not found] <lists.bluez.users.40327430.2090807@grupopie.com>
2004-02-17 20:45 ` Matthew Reimer
[not found] <200402160913.i1G9DCP02222@webserver.restinfor.pt>
2004-02-17 20:06 ` Paulo Marques
[not found] <lists.bluez.users.40323EC2.8080203@csr.com>
2004-02-17 10:50 ` grpmind+bluez.users
2004-02-17 18:58 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 3:42 grpmind+bluez.users
2004-02-17 11:52 ` Marcel Holtmann
2004-02-17 16:18 ` Steven Singer
2004-02-17 17:03 ` Marcel Holtmann
2004-02-17 22:11 ` Steven Singer
2004-02-17 22:51 ` Marcel Holtmann
2004-02-14 17:06 grpmind+bluez.users
2004-02-15 14:33 ` Marcel Holtmann
2004-02-16 22:20 ` Michel Planques
2004-02-16 22:58 ` 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=1077032243.2665.7.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=grpmind+bluez.users@boromir.vpop.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