Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”): Software Version
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other
SDK Manager Version
1.6.0.8170
1.5.1.7815
1.5.0.7774
other
Host Machine Version
native Ubuntu 18.04
other
Hi,
I’ve noticed that in the previous DriveOS document, for example the 5.1.6.0, has a section that describes the ISP interface. But in latter (5.2) versions that section no longer exist. I can also find the ISP sample code on 5.1.6.0 DriveOS image, but not on 5.2 version. But there are ISP related .h files in the drive-t186ref-linux/include on the 5.2 version.
Are old ISP document and example applicable to new DriveOS version? Is there any reason of removing ISP document & sample? I found the ISP functionality is included in SIPL pipeline by registering image with ISP type, Is it not recommended to use ISP directly, and use RegisterImages() with ISP instead?
What about ISP? SIPL usage of ISP is to put images in a buffer queue, config the buffer, and process them in a pipeline manner, am I correct? Can I write my own function that process single image using ISP accelerator with SIPL?
Looking to understand overall capabilities of ISP - what operations can it do ? I know debayer/scale - can it do CSC (color space conversion) - can it do histograms etc ?
How many instances of ISP are there (on xavier) ?
Is there any sample or doc or recommended way of time sharing ISP among multiple cameras ?
Are there any examples/samples which illustrates usage of ISP with other blocks like encoder, GPU, DLA, PVA ?
I would like to pipe camera output to GPU, PVA and encoder all at the same time (i.e. same camera frame going to 3 different frame consumer accelerators). GPU wants it in RGB, Encoder wants it in YUV420. I’m not sure about format required by PVA yet (please let me know what are possible input formats for PVA) . So I would say I need conversion from bayer to RGB ; bayer to yuv 420, and possibly others (which I do not know yet).
Could CSC also handle bayer to yuv420 Nv12 vs Nv21 ? Could it handle converting it to tiled rather than raster ?
I would like to pipe camera output to GPU, PVA and encoder all at the same time (i.e. same camera frame going to 3 different frame consumer accelerators). GPU wants it in RGB, Encoder wants it in YUV420. I’m not sure about format required by PVA yet (please let me know what are possible input formats for PVA) . So I would say I need conversion from bayer to RGB ; bayer to yuv 420, and possibly others (which I do not know yet).
Is there a DW or D-OS sample that gets close this description ?