Hi Piotr, I’m really glad you mentioned xlnx_dpu.c and xlnx_dpu.h. I found those a few days ago (in the linux-xlnx github repo, I think), and I was trying to find a recipe that installs them, but no luck. I didn’t think of manually copying them to the NI kernel and adding them to the NI recipe.
The CONFIG_XILINX_DPU parameter is an issue. It causes a warning that says it’s an unknown object. I think that’s the parameter that tells “PetaLinux“ to install the DPU drivers, and maybe sets a few other kernel parameters. My assumption is that I have to figure out what kernel options Xilinx enables when that parameter is set, and set those accordingly. Kconfig is a mystery to me, so I’ve been putting it off. :-) I think I need to spend a few hours reading up on Kconfig. Right now, the Kconfig files just look like menu entries to me. I don’t see anything that takes those menu entries and writes to defconfig. Again, I just need to read up on Kconfig while my build is running. Regarding the patches, I learned how to do that properly during this effort. I‘ve been writing a lot of them for lately, and I can’t believe it took me so long to try them. I have to say that kas makes patching REALLY easy. I used to use ‘repo’ when I had many remote layers or repositories to keep track of. I’m never using ‘repo’ again. Kas is great. Once I fix the image_tar PSEUDO_ABORT issue and can build the Mender images, I’ll set up the Kas docker image, and use the kas_build_imgs_package.sh script. Thanks for all of the help! I’ve really learned a lot. Cheers, Mike per...@o2.pl wrote: > Hello Mike, > > After short look at current linux-xlnx - it seems that there are not that > many changes needed for DPU to work. The driver is in one C file + C header:\ > linux-xlnx/drivers/misc/xlnx_dpu.c\ > linux-xlnx/drivers/misc/xlnx_dpu.h > > Look at their histories. Initial addition of this driver is in commit > 5ce32fe84b358a041. Previous commit adds device-tree documentation. If I were > doing it myself I would probably first manually copy those files to NI’s > kernel + associated changes in driver/misc/Kconfig and driver/misc/Makefile > > then add CONFIG_XILINX_DPU=y option in the configuration file and compile the > kernel manually. This would probably verify if those two files are all what > is required for DPU to work. Only after that I would add the commits from > linux-xlnx to NI’s kernel source (by cherry-picking them). After that I would > turn them into a series of patches that could be copied into meta-titanium > kernel. > > Best Regards,\ > Piotr Krysik
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
