wireless
Here are 602 public repositories matching this topic...
-
Updated
Sep 3, 2021 - Shell
-
Updated
Apr 18, 2020 - Python
-
Updated
Sep 6, 2021 - C++
-
Updated
Aug 26, 2020 - Java
-
Updated
Nov 3, 2019 - Python
-
Updated
Sep 3, 2021 - Go
-
Updated
Sep 4, 2021 - Kotlin
-
Updated
Apr 23, 2019 - Python
-
Updated
May 13, 2021 - Python
As part of the work in #736 we added a Kconfig setting to keep using the old built in "nano" z_printf implementation, after identifying that our use of format strings didn't work properly w/ the newly introduced CBPRINTF in the newer Zephyr release.
Someone should back out that defaulting, and make ZMK work with the newer printf implementation.
Indicator CC V4 adds two new commands:
- Indicator Description Get Command
- Indicator Description Report Command
TODOs:
- Implement the new commands
- Implement a
getDescriptionmethod onIndicatorCCAPI - update
@implementedVersiondecor
In documentation, it is suggested to use Stouts.postfix from https://github.com/nemesisdesign/Stouts.postfix
In meta/main.yml, it uses https://github.com/Stouts/Stouts.postfix
https://github.com/openwisp/ansible-openwisp2/blob/0df7136ae8bdd43421b535fd499a012fe408e04f/meta/main.yml#L3-L9
This discrepancy should be resolved and the correct URL should be present at both the places.
CSS and Js linting checks are disabled by default from openwisp-qa-check. Check this https://github.com/openwisp/openwisp-utils/#openwisp-qa-check and enable it for controller and remove changes made in openwisp/openwisp-controller#376 related to linting checks. Update readme too.
-
Updated
Apr 24, 2021
-
Updated
Aug 20, 2021 - Python
-
Updated
Apr 27, 2021 - Python
-
Updated
Nov 22, 2019 - Shell
Improve this page
Add a description, image, and links to the wireless topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the wireless topic, visit your repo's landing page and select "manage topics."
A common protocol structure is to have a header containing a
lengthfield, followed by data oflengthbytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.I do not know the best way to address this, but quick and easy way to support