From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Baseband Packets
Date: Sat, 16 Apr 2005 05:56:32 +0200 [thread overview]
Message-ID: <1113623792.16433.49.camel@pegasus> (raw)
In-Reply-To: <12a241ad050415175936c651a1@mail.gmail.com>
Hi Bruno,
> now that I know that bluez supports all types of packets,
> i'm just wondering if it changes the packet type according to the
> sender/receiver devices supported packets info, and if it does, if it
> automatically selects the best packet type according to the
> enviroment, like in a file transfer, for example, according to the BER
> or other error factors. (e.g: DH5 when BER < 10^(-5), or DM1 when BER
> > 10^(-2)).
this is the job of the link manager and it is part of the Bluetooth chip
and not a host stack like BlueZ.
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-16 3:56 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 [this message]
2005-04-18 22:33 ` Anderson Rodrigues
2005-04-18 22:43 ` Marcel Holtmann
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=1113623792.16433.49.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.