[roll] Roll fuchsia [bt][hci] ensure advertising interval values are not the same

Various parts of the Bluetooth Core Spec require that advertising
interval min and max are not the same value. We shouldn't allow it
either. For example, Core Spec Volume 4, Part E, Section 7.8.5: ""The
Advertising_Interval_Min and Advertising_Interval_Max should not be the
same value to enable the Controller to determine the best advertising
interval given other activities.""

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/558242
Original-Revision: e785bfc4a1ce3922594d191ef3a03002c363c9f6
GitOrigin-RevId: 6ce0eecbe4f3b2056b0f96c77d39073a7ae2e688
Change-Id: I7ff48de3e42de8b1632d8118eb411dd11fc8e886
1 file changed
tree: 4b8201388a548159d45df7d046260f24dc818bb0
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. firmware
  8. flower
  9. jiri.lock
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.