07:08 <Marcuss2[m]> <diondokter[m]> "image.png" <- Git gud

07:57 <Ralph[m]> <BogdanOlar[m]> "Thanks! I ended up picking stm3..." <- it depends on whether you want to write an async HAL or not - for async HALs the embassy HALs are probably your best reference (are there even already others out there?), otherwise `stm32f4x-hal` might be a good reference.

07:57 <Ralph[m]> i'm not sure whether it still makes sense to implement the e-h 0.2 traits for a _new_ HAL anymore - just implement the 1.0 traits and help push any driver you plan on using in that direction (by providing PRs, etc. to upgrade them).

10:20 <BogdanOlar[m]> <Ralph[m]> "it depends on whether you want..." <- > <@rursprung:matrix.org> it depends on whether you want to write an async HAL or not - for async HALs the embassy HALs are probably your best reference (are there even already others out there?), otherwise `stm32f4x-hal` might be a good reference.

10:20 <BogdanOlar[m]> > i'm not sure whether it still makes sense to implement the e-h 0.2 traits for a _new_ HAL anymore - just implement the 1.0 traits and help push any driver you plan on using in that direction (by providing PRs, etc. to upgrade them).

10:20 <BogdanOlar[m]> My plan is to implement the blocking API, then `nb`, then maybe `async` (at least that's my understanding of the progression). Not excluding `asinc` but I also don't have any experience with it aside from watching some coding sessions on youtube :)

10:22 <BogdanOlar[m]> In terms of drivers, my development board has a LS013B7DH03 LCD, and was pleased to find that there already exists a new driver for it and it implements embedded-hal 1.0

10:24 <BogdanOlar[m]> The ultimate goal is to program a SkiFree game which uses the capacitive touch pads, also present on the devboard. :)

10:28 <BogdanOlar[m]> remember this? https://i.imgur.com/vycRecs.gif :))

10:29 <BogdanOlar[m]> * My plan is to implement the blocking API, then nb, then maybe async (at least that's my understanding of the progression). Not excluding async but I also don't have any experience with it aside from watching some coding sessions on youtube :)

14:55 <michaeldesilva[m> If I want to serialise data and write to an EEPROM... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/RIMomgKMyUsJGgEAzWyGCZQe>)

14:57 <thejpster[m]> You’ll be limited by the speed of the EEPROM. So the question should perhaps be “do I optimise the transfer for lower power or shorter development time”

14:59 <thejpster[m]> And DMA isn’t a transport, it’s a programmable logic block that can move bytes from one address to another another while the CPU does something else (or sleeps).

16:06 <mameluc[m]> <michaeldesilva[m> "If I want to serialise data..." <- > <@michael.desilva:matrix.org> If I want to serialise data and write to an EEPROM... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/CIARxoEyRFbsfTLhHuJeOpqj>)

16:30 <firefrommoonligh> For interface, internal will be fastest. Then probably Qspi

16:30 <firefrommoonligh> Look into memory mapping Qspi flash for a nice API

16:31 <firefrommoonligh> If using internal, make sure you don't overwrite program memory! Unless you are into self-writing code or something; that would be very cool!

17:49 <holo[m]> Hey im trying to use enums to handle multiple actions on my pico w. On pico W it looks its sendting everything like it should https://pastebin.com/cQiv2yY7 and this is handle by this code: https://github.com/holotrack/switch-embassy-rs/blob/main/src/main.rs#L187... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/UsOQmmixqgJnFlRdSqNsddYl>)

17:50 <holo[m]> * Hey im trying to use enums to handle multiple actions on my pico w. On pico W it looks its sendting everything like it should https://pastebin.com/cQiv2yY7 and this is handle by this code: https://github.com/holotrack/switch-embassy-rs/blob/main/src/main.rs#L187... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/AIidXbniJcgqsmeimagkIakY>)

17:52 <holo[m]> Basially its sending command and when waiting on reply with "read" its getting connection reset by peer even on controller side its looks reply was send properly

17:54 <holo[m]> * Basially its sending command and when waiting on reply with "read" its getting connection reset by peer even on device side it looks reply was send properly

17:58 <Ralph[m]> <BogdanOlar[m]> "remember this? https://i.imgur...." <- of course! i also just recently found out that you can now play the original thanks to archive.org! https://archive.org/details/win3_WINSKI

21:27 <holo[m]> * Basically its sending command and when waiting on reply with "read" its getting connection reset by peer even on device side it looks reply was send properly