Difference between revisions of "JetsonTX2/V4L2 driver support/V4L2 drivers available for Jetson SoCs"
(Created page with "<noinclude> {{JetsonTX2/Head|next=Getting Started|previous=|keywords=}} </noinclude> <table> <tr> <td><div class="clear; float:right">__TOC__</div></td> <td> <html> <div id='...") |
m |
||
| Line 1: | Line 1: | ||
<noinclude> | <noinclude> | ||
| − | {{JetsonTX2/Head|next= | + | {{JetsonTX2/Head|next=|previous=|keywords=}} |
</noinclude> | </noinclude> | ||
| Line 244: | Line 244: | ||
<noinclude> | <noinclude> | ||
| − | {{JetsonTX2/Foot|| | + | {{JetsonTX2/Foot||}} |
</noinclude> | </noinclude> | ||
Revision as of 04:14, 10 July 2019
|
|
Template:Eval SDK Download, Demo Image download and Contact Us buttons |
Capture
This list includes some of the chips that have been tested already on Jetson TX1, Jetson TX2 and Xavier using RidgeRun V4L2 drivers. You can find information about ISP Tuning in this wiki page
- MAX96709/MAX96706 - GMSL1
- MAX96705/MAX9286 - GMSL1
- GMSL2 (work in progress on JP 3.3)
- OV10640 and OV490
- OV10635
- OV5647
- OV5670
- TC358840
- TC358743
- TC358746
- FPGA V4L2 driver
- Galileo2 TCM8647MD
- IMX219
- IMX230
- IMX274
- IMX283
- IMX290
- IMX298
- IMX334
- IMX377
- IMX385
- IMX477
- MT9M021 + Toshiba TC358746
- AR0144
- TW6869
- OS08A10
- AR1335
- MAX98357A-ASoC Driver in Jetson TX1 and TX2
- AR0231 (Sekonix Camera)
- IMX344
- GMSL MAX9288
- OV24A10
- MT9V024
- IMX397
Display
- ADV7535
What happens if the driver I am looking for is not on the list?
RidgeRun has a 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 create it for you.
Feel free to Contact Us if you have a special driver request, we would be glad to help you!
Hardware availability
If you are planning on acquiring an existent driver and extend it with additional functionalities or if you are interested in requesting for 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.
