You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 3, 2024. It is now read-only.
Currently, users are expected to make and manage a single instance of I/O buses (UART, SPI, and I2C) on the RPi. We should change this to be the same as on the BBB, where instances are provided by the I/O system.
Currently, if the user makes two instances, everything works, but thread safety is no longer guaranteed, which can have confiusing effects. That, and the fact that the two platforms use different instantiation patterns is simply confusing.
This will be a breaking change.
The text was updated successfully, but these errors were encountered:
Currently, users are expected to make and manage a single instance of I/O buses (UART, SPI, and I2C) on the RPi. We should change this to be the same as on the BBB, where instances are provided by the I/O system.
Currently, if the user makes two instances, everything works, but thread safety is no longer guaranteed, which can have confiusing effects. That, and the fact that the two platforms use different instantiation patterns is simply confusing.
This will be a breaking change.
The text was updated successfully, but these errors were encountered: