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
This is more like a discussion than an issue, Read the code for Sio and specifically SioFifo.
I was trying to find an inter-core fifo example where instead of a u32 type there is sort of a generic or bytes that I can send and pull. Then I noticed that the SioFifo::write(&mut self, value: u32) only writes bytes to a memory location, and instead of using a generic type the author has gone for a u32. Is there a reason for this u32 usage instead of a generic one?
If it's doable, I am more than willing to contribute and make an infra that supports generics.
The text was updated successfully, but these errors were encountered:
It may be better for both usability and performance to use the SioFifo only for coordination purposes, and do the actual data transfer by passing pointers to memory locations. But I'm not aware of any actual implementations. So having some practical examples would be very welcome!
I am working on giving some examples, I don't think the implementation would differ from the one we have now but don't take my word for it I am a novice in Rust.
I will share here If I managed to pull up something, hopefully this weekend.
This is more like a discussion than an issue, Read the code for
Sio
and specificallySioFifo
.I was trying to find an inter-core fifo example where instead of a
u32
type there is sort of a generic or bytes that I can send and pull. Then I noticed that the SioFifo::write(&mut self, value: u32) only writes bytes to a memory location, and instead of using a generic type the author has gone for au32
. Is there a reason for thisu32
usage instead of a generic one?If it's doable, I am more than willing to contribute and make an infra that supports generics.
The text was updated successfully, but these errors were encountered: