Skip to content

Extend libtapasco with Monitor DMA Engine#299

Draft
zyno42 wants to merge 1 commit into
esa-tu-darmstadt:developfrom
zyno42:feature/libtapasco_monitor_dma_engine
Draft

Extend libtapasco with Monitor DMA Engine#299
zyno42 wants to merge 1 commit into
esa-tu-darmstadt:developfrom
zyno42:feature/libtapasco_monitor_dma_engine

Conversation

@zyno42

@zyno42 zyno42 commented Sep 6, 2021

Copy link
Copy Markdown
Contributor

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.

Implement suggestion of @jahofmann in:
esa-tu-darmstadt#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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant