Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow network buffers to work directly with peripheral memory #225

Open
thirtytwobits opened this issue May 24, 2019 · 0 comments
Open

Allow network buffers to work directly with peripheral memory #225

thirtytwobits opened this issue May 24, 2019 · 0 comments
Labels
class-feature domain-production Pertains to the shippable code rather than any scaffolding priority-low A minor issue

Comments

@thirtytwobits
Copy link
Contributor

image

The above diagram shows how memory is copied from peripheral memory into system memory before it is again copied by the transport layer into the final message data passed to applications. It should be possible to allow a platform to expose the peripheral memory directly to the transport layer using the media layer as an abstract memory view. This will require an abstract means for safely sharing this memory so there's some careful design that has to occur first.

@thirtytwobits thirtytwobits added this to the pre-v1.0.0-1 milestone May 29, 2019
@thirtytwobits thirtytwobits removed this from the pre-v1.0.0-1 milestone Jul 5, 2019
@pavel-kirienko pavel-kirienko changed the title Allow CAN::Frame to work directly with peripheral memory Allow network buffers to work directly with peripheral memory Apr 4, 2024
@pavel-kirienko pavel-kirienko added priority-low A minor issue domain-production Pertains to the shippable code rather than any scaffolding and removed v1 labels Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
class-feature domain-production Pertains to the shippable code rather than any scaffolding priority-low A minor issue
Projects
None yet
Development

No branches or pull requests

2 participants