suspect-devices/circuitpython/extmod/modlwip.c, branch 6.1.0-beta.2

Add license to some obvious files.

2020-07-06T18:16:25+00:00

protocols: Allow them to be (optionally) type-safe

2019-12-04T15:29:57+00:00

Protocols are nice, but there is no way for C code to verify whether a type's "protocol" structure actually implements some particular protocol. As a result, you can pass an object that implements the "vfs" protocol to one that expects the "stream" protocol, and the opposite of awesomeness ensues. This patch adds an OPTIONAL (but enabled by default) protocol identifier as the first member of any protocol structure. This identifier is simply a unique QSTR chosen by the protocol designer and used by each protocol implementer. When checking for protocol support, instead of just checking whether the object's type has a non-NULL protocol field, use `mp_proto_get` which implements the protocol check when possible. The existing protocols are now named: protocol_framebuf protocol_i2c protocol_pin protocol_stream protocol_spi protocol_vfs (most of these are unused in CP and are just inherited from MP; vfs and stream are definitely used though) I did not find any crashing examples, but here's one to give a flavor of what is improved, using `micropython_coverage`. Before the change, the vfs "ioctl" protocol is invoked, and the result is not intelligible as json (but it could have resulted in a hard fault, potentially): >>> import uos, ujson >>> u = uos.VfsPosix('/tmp') >>> ujson.load(u) Traceback (most recent call last): File "", line 1, in ValueError: syntax error in JSON After the change, the vfs object is correctly detected as not supporting the stream protocol: >>> ujson.load(p) Traceback (most recent call last): File "", line 1, in OSError: stream operation not supported

WIP: complete manual inspection of all significant changes

2018-07-24T01:34:25+00:00

extmod/modlwip: Allow to compile with MICROPY_PY_LWIP disabled.

2018-05-21T06:46:30+00:00

extmod/modlwip: Set POLLHUP flag for sockets that are new.

2018-05-17T13:17:36+00:00

This matches CPython behaviour on Linux: a socket that is new and not listening or connected is considered "hung up". Thanks to @rkojedzinszky for the initial patch, PR #3457.

extmod/modlwip: Update to work with lwIP v2.0.

2018-05-17T02:58:34+00:00

lwIP v2.0.3 has been tested with this lwip module and it works very well.

extmod/modlwip: In ioctl handle case when socket is in an error state.

2018-05-04T05:15:04+00:00

Using MP_STREAM_POLL_HUP for ERR_RST state follows how *nix handles this case.

extmod/modlwip: Check if getaddrinfo() constraints are supported or not.

2018-04-23T06:38:20+00:00

In particular don't issue a warning if the passed-in constraints are actually supported because they are the default values.

py/stream: Switch stream close operation from method to ioctl.

2018-04-10T03:41:32+00:00

This patch moves the implementation of stream closure from a dedicated method to the ioctl of the stream protocol, for each type that implements closing. The benefits of this are: 1. Rounds out the stream ioctl function, which already includes flush, seek and poll (among other things). 2. Makes calling mp_stream_close() on an object slightly more efficient because it now no longer needs to lookup the close method and call it, rather it just delegates straight to the ioctl function (if it exists). 3. Reduces code size and allows future types that implement the stream protocol to be smaller because they don't need a dedicated close method. Code size reduction is around 200 bytes smaller for x86 archs and around 30 bytes smaller for the bare-metal archs.

extmod/modlwip: Commit TCP out data to lower layers if buffer gets full.

2017-11-24T04:52:32+00:00

Dramatically improves TCP sending throughput because without an explicit call to tcp_output() the data is only sent to the lower layers via the lwIP slow timer which (by default) ticks every 500ms.