summaryrefslogtreecommitdiffstats
path: root/include/net/ieee80211.h
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2008-07-14 20:13:46 +0200
committerMarcel Holtmann <marcel@holtmann.org>2008-07-14 20:13:46 +0200
commita8746417e864da1ed36dd2432a399fbeb843c2a0 (patch)
treee0e392e8b76d53748f357e888483bced2de24e2b /include/net/ieee80211.h
parent9dc0a3afc08d6c20c284994dcd84531787d00ec2 (diff)
downloadtalos-op-linux-a8746417e864da1ed36dd2432a399fbeb843c2a0.tar.gz
talos-op-linux-a8746417e864da1ed36dd2432a399fbeb843c2a0.zip
[Bluetooth] Track connection packet type changes
The connection packet type can be changed after the connection has been established and thus needs to be properly tracked to ensure that the host stack has always correct and valid information about it. On incoming connections the Bluetooth core switches the supported packet types to the configured list for this controller. However the usefulness of this feature has been questioned a lot. The general consent is that every Bluetooth host stack should enable as many packet types as the hardware actually supports and leave the decision to the link manager software running on the Bluetooth chip. When running on Bluetooth 2.0 or later hardware, don't change the packet type for incoming connections anymore. This hardware likely supports Enhanced Data Rate and thus leave it completely up to the link manager to pick the best packet type. Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'include/net/ieee80211.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud