-
Updated
Oct 16, 2020 - C++
embedded
Here are 2,510 public repositories matching this topic...
-
Updated
Oct 17, 2020 - C
-
Updated
Jun 28, 2020 - Python
-
Updated
Oct 16, 2020 - C++
-
Updated
Oct 16, 2020 - C++
-
Updated
Oct 13, 2020 - C
-
Updated
Oct 16, 2020 - C
-
Updated
Oct 16, 2020 - 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
Oct 6, 2020 - Python
-
Updated
Oct 14, 2020 - C++
-
Updated
Oct 17, 2020 - Java
-
Updated
Oct 13, 2020 - C++
Python 3 bindings
Implement Python 3 bindings, so wasm3 can be easily used from Python.
Resurrecting the second bullet from #1334
- Figure out how to fix favicon / logo more generally (here's a start https://github.com/tock/tock/tree/doc-updates)
-
Updated
Oct 16, 2020 - C++
-
Updated
Sep 9, 2020 - C
-
Updated
Oct 17, 2020 - C++
-
Updated
Oct 16, 2020 - C
-
Updated
Sep 17, 2020 - C
Credits to Brian — Brian Dean [email protected] BDMICRO, LLC https://www.bdmicro.com
According to the datasheet for the MX25R1635F, the JDEC should be 0xc2, 0x28, 0x15. In the devices.h file, the capacity parameter is specified as 0x18 for that chip. So the value is incorrect in devices.h
/ Settings for the Macronix MX25R1635F 8MiB SPI flash.
// Datasheet: https://www.macronix.com/Lists/Dat
-
Updated
Oct 16, 2020
-
Updated
Oct 16, 2020 - C
Dhcpv4Client ignores the device checksum capabiltities, and always uses the default value for ChecksumCapabilities. The code responsible can be seen here:
https://github.com/smoltcp-rs/smoltcp/blob/bdfa44270e9c59b3095b555cdf14601f7dc27794/src/dhcp/clientv4.rs#L133
As far as I can tell, this would basically be a one-line fix:
let checksum_caps = iface.device().capabilities().check-
Updated
Sep 28, 2020 - C
-
Updated
Jul 20, 2020 - Jupyter Notebook
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下面。