We found the image raw16 data output from sensor is different from the data we get from v4l2.
For example, one pixel of output data from sensor is
0x201c,
but the pixel we get from v4l2 is
0x1c10.
We guess maybe xavier move low eight bits(0x1c) to the high eight bits, and use the original high eight bits subtract 16, then move to the low eight bits.
why does xavier do this? The shift operation is easy to understand, but why is there subtraction?
The attachments are image output from sensor and get from v4l2.
We add one item like this in 《vi5_formats.h》 to support raw16,
We use “T_R16” to process raw16 data, but we cannot find how “T_R16” process raw16 data. We can only find “T_R16_I” in datasheet, but “T_R16_I” cannot process raw16. image.7z (7.21 KB)
I don’t know how to modify the DT if configure VI to T_R32, and I can’t find anything about it in the web you send.
I think the configurations don’t need to be changed, because the input from sensor doesn’t changed. And I should use 4 bytes to store a image in v4l2 software. I did this but failed.