start adding argument and response module#232
start adding argument and response module#232robamu wants to merge 1 commit intorust-embedded-community:developfrom
Conversation
robamu
force-pushed
the
argument-response-module
branch
from
2e7bd36 to
1ba799f
Compare
| //============================================================================== | ||
|
|
||
| /// Argument module. Arguments are additional command parameters. | ||
| pub mod argument { |
There was a problem hiding this comment.
I’d rather have modules on disk instead of inline modules. I just it makes them easier to find in your editor?
robamu
force-pushed
the
argument-response-module
branch
2 times, most recently
from
c0d50f5 to
b9d7961
Compare
|
Looks good, but I see these types aren't yet used. Is there a plan to use them? |
|
for now, these can be used for implementing SD drivers in separate crates. Implementing a generic SD driver which use these inside the library could work, but a generic transport trait to send CMDs/ACMDS is required first and I am not fully sure how well that works. |
robamu
force-pushed
the
argument-response-module
branch
3 times, most recently
from
d322f44 to
9300e6a
Compare
robamu
force-pushed
the
argument-response-module
branch
from
9300e6a to
f1bb923
Compare
robamu
force-pushed
the
argument-response-module
branch
2 times, most recently
from
b88fa22 to
1320605
Compare
robamu
force-pushed
the
argument-response-module
branch
from
1320605 to
d5b63d9
Compare
|
rebased again |
| MaximumPerformance = 1, | ||
| } | ||
|
|
||
| /// HPC. |
|
Looks ok, but I think we need some kind of example to show how to use them. How hard would it be to build a fake SD Card with an API to send requests and get responses that an example can drive in a similar way to how you would initialise an actual SD Card? |
2 participants
Nice types for SD mode arguments and responses using
bitbybit