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

Add third party vc mipi nvidia module, how to add porting? #118

Open
lipingioiopeter opened this issue Aug 28, 2024 · 0 comments
Open

Add third party vc mipi nvidia module, how to add porting? #118

lipingioiopeter opened this issue Aug 28, 2024 · 0 comments

Comments

@lipingioiopeter
Copy link

IDE:jeston 36.0
JetPack6.0
core board:orin Nano4GB
board:Jetson Orin Nano Developer Kit
kernel source: Jetson Linux 36.3 NVIDIA Developer
rootfs source: Basic Flavor Root File System Root File System — NVIDIA Jetson Linux Developer Guide 1 documentation
I am a beginner and recently used an imx477 camera in a project. While searching for information, I found someone using vc-mipi-nvidia to implement the camera driver.
I according to the GitHub - VC-MIPI-modules/vc_mipi_nvidia: Vision Components MIPI CSI-2 driver for NVIDIA Jetson Nano, Xavier NX, AGX Xavier, TX2 and Orin Nano, Orin NX website guidance for migration, module migration found the following problems.:

1.According to the tutorial, I will copy in the device tree to/hardware/nvidia/t23x/nv - public/overlay path, but his third department all the driver file copy to * * / kernel/nvidia/drivers/media/i2c path, In my actual kernel there is no such path but: Linux_for_Tegra/source/kernel/kernel - jammy - SRC/drivers/media/i2c, I also found a path Linux_for_Tegra/source/nvidia-oot/drivers/media/i2c, which path do I need to copy the file to? Or are neither of these paths correct?
2.Do I need to change the Makefile and Kconfig if I copy the file to the appropriate location?

@github-staff github-staff deleted a comment Aug 28, 2024
@github-staff github-staff deleted a comment from lipingioiopeter Aug 28, 2024
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

No branches or pull requests

1 participant