From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Baseband Packets
Date: Tue, 19 Apr 2005 00:43:56 +0200 [thread overview]
Message-ID: <1113864236.16233.148.camel@pegasus> (raw)
In-Reply-To: <d1f423d305041815331d2e6698@mail.gmail.com>
Hi Anderson,
> The spec says that: "Quality measurements in the receiver of one
> device can be used to dynamically control the packet type transmitted
> from the remote device for optimization of the data throughput."
>
> The question is, is it done automatically or not? May we assume that
> LM is smart enough to measure the RF channel and based on it changes
> automatically the packet type ?
the link manager should be smart enough, but choosing the right packet
type is a science by itself.
> If not, is there any point in bluez that we can talk with LM?
We can only limit available packet types, but this makes no sense at all
and should never be done.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
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-18 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 0:59 [Bluez-devel] Baseband Packets Bruno Abinader
2005-04-16 3:56 ` Marcel Holtmann
2005-04-18 22:33 ` Anderson Rodrigues
2005-04-18 22:43 ` Marcel Holtmann [this message]
2005-04-18 23:34 ` Anderson Rodrigues
2005-04-18 23:55 ` 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=1113864236.16233.148.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 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.