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

Replace PULP cluster DMA #81

Open
1 of 3 tasks
adimauro-iis opened this issue Jun 24, 2024 · 3 comments
Open
1 of 3 tasks

Replace PULP cluster DMA #81

adimauro-iis opened this issue Jun 24, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@adimauro-iis
Copy link

adimauro-iis commented Jun 24, 2024

  • Integrate the iDMA
  • multi-initiator arbiter in HCI for full-bandwidth DMA access
  • Write bare-metal tests
@adimauro-iis adimauro-iis added the enhancement New feature or request label Jun 24, 2024
@FrancescoConti
Copy link
Member

@arpansur @da-gazzi we can move the technical discussion here maybe... and link any PR e.g., in HCI for the multi-initiatior arbiter.

@FrancescoConti FrancescoConti self-assigned this Jul 11, 2024
@FrancescoConti
Copy link
Member

Also.. @adimauro-iis if an issue actually involves more than one repo, do we capture that here?

@adimauro-iis
Copy link
Author

adimauro-iis commented Jul 11, 2024

Good point, I like a lot the idea of associating an issues to specific code changes into a repo.

I think that whenever an issue requires changes into another repo we could:

  1. Consider those changes as a pre-requisite for the issue, and assume they will be handled separately
  2. Track them here, i.e. open an issue in the new repo and link it here as part of the task list, making them a sort of "sub-issue"

Option 2 tracks everything but require more diligence...I am fine with both

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants