V4L2 drivers available for NVIDIA Jetson SoCs

From RidgeRun Developer Wiki
Revision as of 11:01, 13 December 2019 by Spalli (talk | contribs)





Warning
You can find the full list of drivers, in the List of Tested Camera Sensors section of our RidgeRun Linux Camera Drivers wiki. Visit this wiki for more details on related driver services.


V4L2 drivers for the capture chips

This list includes some of the chips that have been tested already on NVIDIA Jetson TX1, Jetson TX2, and Xavier using RidgeRun V4L2 drivers. See also Jetson ISP Tuning

Thermal Cameras

Typically used with the TC358746 (parallel to MIPI CSI) RidgeRun has experience creating V4L2 Drivers for:

  • FLIR Tau640
  • FLIR Tau320

Color & Monochrome

Radars

V4L2 drivers for the display chips

  • ADV7535

If the driver I am looking for is not on the list?

RidgeRun has wide experience in the development of kernel drivers, if the driver you are looking for is not on the list, it is most likely because we haven't received a request for it yet, but we can develop the new driver for you.

RidgeRun contact details are provided in the Contact Us section at the end of this wiki for requesting a new driver development.

Hardware availability

If you are planning on acquiring an existent driver and extending it with additional functionalities or if you are interested in requesting the creation of a totally new driver, please take into account that it might be necessary to send the required hardware to our offices to make sure our engineering team can test, debug and validate the driver.

ISP calibration

RidgeRun will use the default ISP calibration. Please notice that once the driver is in place you might need to create a custom ISP calibration file for your sensor if you need to use the built-in ISP. NVIDIA gives access to the ISP calibration tools only to ODMs, so companies like D3engineering and Leopard Imaging can create this file for you if the default settings don't produce the expected image quality.

How to port a driver to JetPack 6.0

In the JetPack 5 era, drivers were directly integrated into NVIDIA’s downstream kernel either built directly into the kernel image or built as in-tree module, but NVIDIA wants to align with the upstream kernel so users can choose the kernel version on their own. This means that on JetPack 6.0 a lot of drivers are being pulled out from the kernel source, which must be compiled separately as out-of-tree modules.

The Out of Tree modules scheme made significant modifications on how a driver is included to the kernel sources, feel free to read the following wiki if you wish to find out further details and instructions

If you need assistance or you wish to port your driver to any JetPack version check the Contact Us section in order for you to hire our services. We provide support as T&M and also as an Engineering Subscription.

See also


RidgeRun Resources

Quick Start Client Engagement Process RidgeRun Blog Homepage
Technical and Sales Support RidgeRun Online Store RidgeRun Videos Contact Us
RidgeRun.ai: Artificial Intelligence | Generative AI | Machine Learning

Contact Us

Visit our Main Website for the RidgeRun Products and Online Store. RidgeRun Engineering information is available at RidgeRun Engineering Services, RidgeRun Professional Services, RidgeRun Subscription Model and Client Engagement Process wiki pages. Please email to support@ridgerun.com for technical questions and contactus@ridgerun.com for other queries. Contact details for sponsoring the RidgeRun GStreamer projects are available in Sponsor Projects page.



  Index