Extend libtapasco with Monitor DMA Engine #299
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement suggestion of @jahofmann in:
#296 (comment)
When a new device is created a dummy implementation of the DMA Engine is
used that simply does nothing. The actual DMA Engine is initialized
later when the access mode is changed from monitor to exclusive mode.
This is necessary to prevent a monitoring application like
tapasco-debug
to allocate all DMA Buffers of the kernel driver.