16:09 <AstraKernel[m]> Working on Max7219 driver. Which one make sense and better? Indexing from left-to-right or right-to-left or it does not matter?... (full message at <https://catircservices.org/_irc/v1/media/download/AWe7hRdF2_0WfCEYCFwwJp29ji55UQ6fzinbnf-6R-V8tSPqQ4plT_3cRJuORY88UkALdIviNWIkfm1nvjcNfnO_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9PSmxJTmJTdUZtbWRLR0FVQWR5b2Vkem4>)

17:02 <JamesMunns[m]> It's a Common Problem: https://mastodon.social/@acegikmo/109429307211544506 :D

17:05 <JamesMunns[m]> But yeah, idk, for personal projects I would probably do it in whatever order makes it easier to implement or use. If those act like shift registers, then the first photo you posted (0 on the left) actually makes sense to me, since it means you push data out in 0, 1, 2, 3 order, and that matches what the user sees.

17:07 <AstraKernel[m]> It is personal project. At the same time sharing the knowledge with others through the Rust embedded drivers book. While trying to explain it in the book, the second seems more simple. Especially it well fits with embedded graphics co ordinates and framebuffer flow

17:12 <AstraKernel[m]> s/second/*first/

17:12 <AstraKernel[m]> Thanks then I will go with first

17:14 <andwass[m]> I find the first to be more easy to remember. Especially if you read from left to right then the left-most is the lowest number and so on.

17:26 <dngrs[m]> "just rotate the display 180 degrees if you prefer something different"

19:32 <barafael[m]> huh. I updated one of my applications today, specifically I updated postcard. When updating from 1.1.1 to 1.1.2, I observe that my application suddenly becomes way slower and seems to calculate cobs frames differently. I see that the cobs dependency of postcard changed a lot in between. Anybody else observed something like this?

19:33 <barafael[m]> I am doing something considered funky though - I'm using cobs encoding to create a tokio_util::codec::Codec

19:35 <barafael[m]> i'll be bisecting the cobs crate changes... on a whim

19:37 <JamesMunns[m]> If you find something let me know!

19:51 <barafael[m]> https://github.com/jamesmunns/cobs.rs/commit/b964630a3a4538129987b6f99253df41851314c8 is the commit where my code stops being cool. Confirming the suspicion that it has to do with framing

20:09 <barafael[m]> I'm getting one DeserializeBadEncoding error per message, roughly. James Munns am I holding it wrong or what?

20:10 <JamesMunns[m]> Can you give me a runnable repro or some example code/input? Hard to tell if you're holding it wrong otherwise :D

20:10 <barafael[m]> working on that

20:11 <JamesMunns[m]> Are you sending empty frames, or duplicate zeroes on encoding?

20:12 <barafael[m]> no, i don't think so. Even the unit enum values should not be empty frames in postcard. And duplicating zeroes would be something I'd have to do manually, right

20:13 <JamesMunns[m]> Likely!

20:32 <firefrommoonligh> I'm wish James. There are no established conventions here, so follow your heart, and don't second-guess whichever choice you make

20:32 <firefrommoonligh> Also, Big Endian 4 lyfe! Suck it LE n00bs

20:32 <firefrommoonligh> s/wish/with/

20:35 <RobinMueller[m]> barafael: if you keep running into the issue, i can also look into it.

20:35 <GuineaWheek[m]> does ANYBODY in this channel develop for a BE target

20:36 <GuineaWheek[m]> didn't think so

20:36 <GuineaWheek[m]> at least, hopefully not by choice

20:37 <barafael[m]> RobinMueller[m]: Currently isolating it to a repro, I'll keep posted here what I find. Thanks so much.

22:22 <barafael[m]> James Munns: here I reduced the case to an absolute minimum:

22:22 <barafael[m]> https://github.com/barafael/postcard-1.1.1-to-1.1.2-possible-breakage-repro

22:23 <barafael[m]> it's a repo with a firmware, a protocol, and a client, just like my actual code, but greatly simplified. (Please if you don't mind the advice, take this opportunity to NOT get nerd sniped on an early monday in case you are in EU timezones right now).