suspect-devices/circuitpython/ports/stm32/modnetwork.c, branch azure CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=azure 2018-06-03T11:50:49+00:00 stm32/modnetwork: Fix arg indexing in generic ifconfig method. 2018-06-03T11:50:49+00:00 Damien George damien.p.george@gmail.com 2018-06-03T11:50:49+00:00 urn:sha1:309fe39dbb14b1f715ea09c4b9de235a099c01b0 stm32/modnetwork: Provide generic implementation of ifconfig method. 2018-06-01T03:33:14+00:00 Damien George damien.p.george@gmail.com 2018-06-01T03:33:14+00:00 urn:sha1:d9f1ecece2f86d3c007ec51853ec499f1aebb21b All it needs is a lwIP netif to function. stm32/modnetwork: Don't take netif's down when network is deinited. 2018-06-01T03:27:06+00:00 Damien George damien.p.george@gmail.com 2018-06-01T03:27:06+00:00 urn:sha1:6d87aa54d6a9d7219b93d7f3141b46afa9c70c48 It should be up to the NIC itself to decide if the network interface is removed upon soft reset. Some NICs can keep the interface up over a soft reset, which improves usability of the network. stm32: Integrate lwIP as implementation of usocket module. 2018-05-21T07:36:06+00:00 Damien George damien.p.george@gmail.com 2018-05-21T06:48:24+00:00 urn:sha1:cda964198a36e8d1ce4497d90484fae4b9d661a5 This patch allows to use lwIP as the implementation of the usocket module, instead of the existing socket-multiplexer that delegates the entire TCP/IP layer to the NIC itself. This is disabled by default, and enabled by defining MICROPY_PY_LWIP to 1. When enabled, the lwIP TCP/IP stack will be included in the build with default settings for memory usage and performance (see lwip_inc/lwipopts.h). It is then up to a particular NIC to register itself with lwIP using the standard lwIP netif API. all: Remove inclusion of internal py header files. 2017-10-04T01:37:50+00:00 Damien George damien.p.george@gmail.com 2017-10-04T01:37:50+00:00 urn:sha1:a3dc1b1957d2c96d7c60c2c629c95077b03488a1 Header files that are considered internal to the py core and should not normally be included directly are: py/nlr.h - internal nlr configuration and declarations py/bc0.h - contains bytecode macro definitions py/runtime0.h - contains basic runtime enums Instead, the top-level header files to include are one of: py/obj.h - includes runtime0.h and defines everything to use the mp_obj_t type py/runtime.h - includes mpstate.h and hence nlr.h, obj.h, runtime0.h, and defines everything to use the general runtime support functions Additional, specific headers (eg py/objlist.h) can be included if needed. ports: Make new ports/ sub-directory and move all ports there. 2017-09-06T03:40:51+00:00 Damien George damien.p.george@gmail.com 2017-09-06T03:40:51+00:00 urn:sha1:01dd7804b87d60b2deab16712eccb3b97351a9b7 This is to keep the top-level directory clean, to make it clear what is core and what is a port, and to allow the repository to grow with new ports in a sustainable way.