implement get_destination_status #177
No reviewers
Labels
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: M-Labs/artiq-zynq#177
Loading…
Reference in New Issue
No description provided.
Delete Branch "mwojcik/artiq-zynq:rtio_destination_status"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As a small break from the axi stuff, I tackled the other issue from the original thread - get_destination_status not being implemented (being hardcoded to return true on destination == 0).
This one was just a bit tricky - yeah I used messages, but to use messages/channels freely, the code must be a part of the
kernel
submodule in runtime, since channels are not publicstatics
and I would rather keep them that way. So that was moved there. Not sure if this could be condensed nicely somewhere else, instead of making a new module.Tested on Kasli-SoC master with connected Kasli 1.1 satellite. The function in experiments (in Python) does behave as intended.
@ -0,0 +1,19 @@
use super::{KERNEL_CHANNEL_0TO1, KERNEL_CHANNEL_1TO0, Message};
pub extern fn get_destination_status(destination: i32) -> bool {
It's just one small function, what about just putting it in
src/kernel/core1.rs
?@ -14,3 +14,3 @@
use super::dma;
use super::cache;
use super::core1::get_destination_status;
Keep the rtio_ prefix?