-
Updated
Mar 4, 2021 - C++
embedded
Here are 2,827 public repositories matching this topic...
-
Updated
Mar 6, 2021 - C
-
Updated
Feb 6, 2021 - Python
-
Updated
Mar 5, 2021 - C++
-
Updated
Mar 6, 2021 - C
-
Updated
Mar 6, 2021 - C
-
Updated
Mar 5, 2021 - C++
-
Updated
Mar 2, 2021 - C++
-
Updated
Mar 4, 2021 - Python
Is your enhancement proposal related to a problem? Please describe.
Refer to: zephyrproject-rtos/zephyr#28932
Describe the solution you'd like
Refer to: zephyrproject-rtos/zephyr#28932 (comment)
Describe alternatives you've considered
NA
Additional context
NA
-
Updated
Mar 3, 2021 - C++
-
Updated
Mar 5, 2021 - Java
-
Updated
Jan 3, 2021 - C++
With Tock running on this board with virtual_uart sitting on top of USB, the Nano 33 BLE is a reasonably promising board to be a standard, well supported Tock board. Additionally, if the board turns out to not be great, the infrastructure which would make the Nano 33 BLE work well would apply to any other board that has the nRF52840 + USB combination.
- Make the bootloader and tockloader ex
-
Updated
Mar 5, 2021 - C++
-
Updated
Mar 7, 2021 - C++
As it is possible to use read/write from the internal storage i guess it would be useful to have a library that handles configuration files.
-
Updated
Jan 16, 2021 - C
-
Updated
Feb 3, 2021 - C
-
Updated
Feb 25, 2021
-
Updated
Feb 22, 2021 - C
-
Updated
Mar 6, 2021 - C
On Linux, packets that stay local to the machine (moving from the host to a container for example) don't always have their checksum computed, see for example https://patchwork.ozlabs.org/patch/261822/.
The proper fix would be to check for TP_STATUS_CSUMNOTREADY, but an easy workaround is to have a way to change the ChecksumCapabilities or DeviceCapabilities.
As a rust noob here my solution for
-
Updated
Feb 25, 2021 - C
Improve this page
Add a description, image, and links to the embedded topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the embedded topic, visit your repo's landing page and select "manage topics."
paddle-mobile将开发一个新的版本,为了:
因此,paddle-mobile将会进行一次完全的重构,从框架设计到代码开发。在新版本开发完成后,将会删除原有mobile-deep-learning的代码。新版本开发期间,代码将放置在paddle-mobile repo的一个子目录下。对于子目录的命名,目前有3个候选,希望大家投票:
有更好的建议,请回复issue。相关issue:#121
另外,待新版本代码开发完成,移除老版本mobile-deep-learning代码后,新版本代码将移出子目录,直接放置在paddle-mobile repo下面。