Uthedris
Uthedris
I’ve been following the thread and figured that I’d throw in my two cents…. The issue is that what Raspberry Pi calls I2C is actually SMB (which always sends the...
> On 15 Dec 2021, at 16:37, Michael Naylor ***@***.***> wrote: > > Similar situation with an INA266. > > — > You are receiving this because you commented. >...
I cleaned to the function to get rid of the warnings and added it to my Safer i2c pull request. And as you say, I really appreciate @uraimo effort to...
The change are not in my main branch yet. If you change your dependency line to: .package( url: "https://github.com/curuvar/SwiftyGPIO.git", branch: "Safe-I2C" ), You should get the added call. > On...
I am happy that I was able to help. I created my own fork because there were some changes I needed to make to do what I needed. It took...
I added the readRaw function to allow multi-byte reads without sending a register number
I merged these changes to PWM with version 1.3.7 on my fork. I had to fix a few types so it would work in 64 bits. I can now control...
Perhaps dupe of #16331
I just like the second because it tells me "you forgot the & again!" Actually, from a purely semantic point of view, I don't like the address-of operator in either...
I did read that. It says that slices are related to pointers, not that they are pointers. It also says “Use &s to obtain a single item pointer”, not to...