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
For at least one device, it would make sense to expose the underlying Tx method. This device writes 3 or 4 bytes to prepare for reads. This can be done with the i2c API as is stands with a pair of Write and Read*Device method calls, but since the underlying Tx method of the driver.Conn exists, it would be nice to be able to use that instead.
We are not maintaining these packages anymore. @maruel was able to take it further and published https://periph.io/ instead. Please take a look at periph.io.
For at least one device, it would make sense to expose the underlying
Tx
method. This device writes 3 or 4 bytes to prepare for reads. This can be done with the i2c API as is stands with a pair ofWrite
andRead
*Device
method calls, but since the underlyingTx
method of thedriver.Conn
exists, it would be nice to be able to use that instead.Would this be possible?
/cc @rakyll
The text was updated successfully, but these errors were encountered: