<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/shared-module/canio/Message.c, branch 6.1.x</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.1.x</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.1.x'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2020-09-28T22:22:00+00:00</updated>
<entry>
<title>CAN: Use mp_obj_t insteaed of canio_message_obj_t, get rid of rtr field</title>
<updated>2020-09-28T22:22:00+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2020-09-28T22:14:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=f4e36fc7f6719cb938b6e11b3e5242b149600d7d'/>
<id>urn:sha1:f4e36fc7f6719cb938b6e11b3e5242b149600d7d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>canio: RemoteTransmissionRequest: Split implementation, keep one structure</title>
<updated>2020-09-28T22:22:00+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2020-09-26T14:44:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=a4cc3ad6cb75845e0dc75ede97b8287bb1af0317'/>
<id>urn:sha1:a4cc3ad6cb75845e0dc75ede97b8287bb1af0317</id>
<content type='text'>
This already begins obscuring things, because now there are two sets of
shared-module functions for manipulating the same structure, e.g.,
common_hal_canio_remote_transmission_request_get_id and
common_hal_canio_message_get_id
</content>
</entry>
<entry>
<title>canio: Split RemoteTransmissionRequest to its own class</title>
<updated>2020-09-28T22:22:00+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2020-09-24T20:25:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=8d45be1cd99c6fbfcb69877ab335e010810c54fd'/>
<id>urn:sha1:8d45be1cd99c6fbfcb69877ab335e010810c54fd</id>
<content type='text'>
It reuses most of canio.Message's implementation, and structure
</content>
</entry>
<entry>
<title>canio: rename from _canio</title>
<updated>2020-09-21T21:44:26+00:00</updated>
<author>
<name>Jeff Epler</name>
<email>jepler@gmail.com</email>
</author>
<published>2020-09-21T21:42:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=4869dbdc670bfa8a5f2e0a639495d03984ea0a6a'/>
<id>urn:sha1:4869dbdc670bfa8a5f2e0a639495d03984ea0a6a</id>
<content type='text'>
This reflects our belief that the API is stable enough to avoid incompatible changes during 6.x.
</content>
</entry>
</feed>
