Update XDMA Makefile to install kernel module to depmod visible location #327
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks, I needed your solution badly! I was wondering if I am the only one in the world who needs to restart and automatically load the xdma driver? Or do others just not restart or patiently run the script |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The previous installation directory (
/lib/modules/$(shell uname -r)/xdma) was not by default searched bydepmodto load a kernel module. This changes the path to*/updates/kernel/drivers/xdmas.t. it can be discovered bydepmod(depmodsearches in theupdatesfolder). This matches the same installation behavior as the XVSEC Makefile: https://github.com/Xilinx/dma_ip_drivers/blob/03ac7f31e256c5604eeb970e98d343cf925ddb52/XVSEC/linux-kernel/Makefile#L9C2-L9C92