Jas Strong

The struct in the firmware follows the conventional C rules for member alignment, and PixelPusher is a 32-bit machine, so the strip flag array is aligned on 4. > On...

It's literally just struct alignment. You have the source to this function in the firmware- you could take a look. Actual PixelPusher only ever supports eight strips, so it will...

That's because the compiler version changed and the new compiler ignored the __packed annotation that RVCT used to respect... > On Jan 17, 2022, at 14:05, Rus Maxham ***@***.***> wrote:...

It does not, because the element before it is not word-aligned. > On Jan 17, 2022, at 20:28, Shawn Silverman ***@***.***> wrote: > > > That's the thing. "Struct alignment"...

Byte arrays are four-byte aligned because sizeof(uint8_t *) == 4 > On Jan 18, 2022, at 08:38, Shawn Silverman ***@***.***> wrote: > > > Here’s how I understand this; what...

sure, but that's not the behaviour that RVCT has. RVCT isn't (or at least wasn't, as of 3.0 or whatever version I was using in 2013) GCC or Clang. >...

It treats the byte array like a single object of sizeof(n). > On Jan 18, 2022, at 10:58, Shawn Silverman ***@***.***> wrote: > > > Ok, I hear you. Sounds...

I have tried every May and every June release so far of HomeAssistant and none of them have worked with the Honeywell Lyric integration. I have to revert to 2024.4.4...

Having just installed, and then immediately rolled back, 2024.6.3, with the exact same consequences, what information would you like me to extract? It's easy enough to install the updated core...