Merge from upstream pine64/bl_iot_sdk #27
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Jesus Velazquez <jesus.velazquez@gmail.com>
This adds some basic checks to the subroutines of eap_input to check that we have requested or agreed to doing EAP authentication before doing any processing on the received packet. The motivation is to make it harder for a malicious peer to disrupt the operation of pppd by sending unsolicited EAP packets. Note that eap_success() already has a check that the EAP client state is reasonable, and does nothing (apart from possibly printing a debug message) if not. Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
bl_sys_time.c: adds null pointer checks and extra spaces cleanup
Fix buffer overflow in EAP
As seen in `inode_del` (and `inode_alloc`), a free (`NOT_INIT`) node can be found anywhere in `g_vfs_dev_nodes`; it’s a “sparse” list. So when checking for free nodes, the iterating index variable (`e`) shall be used, not the counter (`count`). The code got that wrong. For instance, if the first node is not available (type is not `VFS_TYPE_NOT_INIT`), then the function previously returned 0, no matter what, and was iterating the node list in vain.
The ipv6cp-accept-local option was supposed to enable it, but it is already enabled by default, with no way to disable it. For coherency with IPv4 and IPX, this disables ipv6cp-accept-local by default, and the option can be used to enable it. This also enables it automatically when the local id is not specified, in coherency with IPv4 and IPX, and as the documentation was saying. Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
The file's uint32_t alignment should be more restrictive than the uint16_t alignment, so this SHOULD be safe ... and reduces build noise. Co-authored-by: Robert Lipe <robertlipe@gpsbabel.org>
- to enable calling like ./flash_build.py
Remove trailing whitespaces from bl602
.c and .h get tabs expanded to four spaces for consistency, traliing whitespace whacked.
Makefiles do NOT get tabs changed.
image_conf, make_scripts_riscv - Delete trailing spaces. Change tabs to 4 space multiples.
.c and .h get tabs expanded to four spaces for consistency, traliing whitespace whacked.
Makefiles do NOT get tabs changed.
HTML files: remove trailing spaces.
Clean whitespace in customer_apps
Clean components: fix whitespace in components/
fix issue #18
add ble mesh node demo
No scripts actually use this version: the one reference to it, which I've also removed in this commit, was commented out. Having the binary version is confusing because it indicates a proprietary component where there is none. It's also of limited use, since it only works on 64-bit Linux (and, at least on my system, doesn't even run properly there). I disassembled the bytecode of the compiled version and the source version and verified that they are identical, so we are losing nothing with this deletion.
Remove pyinstaller-packed binary version of flash_build.py
It's questionable that dependencies get installed automatically during the build in the first place, but since they do we should at least fail the build with an error if installation fails. This makes the current CI issue on macOS much clearer to diagnose.
We should eventually just get rid of the "pip install" invocation in the Makefile altogether and replace it with good documentation for manual environment setup. Bot for the moment we have it and so we should make it work even in the case where it needs to compile code. This should fix the CI problems on macOS and Ubuntu 19.10. I was torn between fixing it this way and removing the "export"s from the Makefile altogether, replacing them with explicit variable passing to submakes. But I figure that it's probably correct to have $CC and friends automatically set to the cross compiler since the entire purpose of these Makefiles is to build code for the BL602. If we ever delegate some functionality to a shell script, it'll be nice to just have $CC automagically set. So I've kept the exports and fixed it this way instead.
Merge in a number of upstream changes from Bouffalo, resolving conflicts. Most conflicts came from warring whitespace fixes, which is better than no whitespace fixes in either repo. I generally took the upstream version in such cases to make future merges easier. I have left out all upstream docs changes from this merge, since those will have to be separately merged into our bl602-docs submodule.
The latest upstream changes added one project (bl602_demo_blemeshnode) without a genromap. Add one by copying the provided genblenode script. Also make the genromap executable for two other newly-added projects.
commit f90cec6 ("limit amount of make jobs") in our fork added a new environment variable check to all the genromap scripts to limit the number of parallel jobs. Port this check onto the new projects added by upstream in the latest merge.
Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
dacut
pushed a commit
to dacut/bl_iot_sdk
that referenced
this pull request
Jun 30, 2023
add ble mesh node demo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.