Here's what I want:
Get the camera image directly from /dev/video0 without going through the libcamera isp path.
My camera comes with an internal data processing process and there is no need to use the Raspberry Pi's internal isp again for image processing.
In the earlier official documentation, it was described like this.
I've found that this doesn't work on the Raspberry Pi 5. The Raspberry Pi's built-in isp becomes a required path.
I ported the driver to a Raspberry Pi 5 only to see that /dev/video0 can't be used to fetch images directly. From my observations using media-ctl, the new path is:
Is there any way to achieve the functionality I want?
Or is the Raspberry Pi planning to ditch support for mipi cameras that are not libcamera mechanisms?
Get the camera image directly from /dev/video0 without going through the libcamera isp path.
My camera comes with an internal data processing process and there is no need to use the Raspberry Pi's internal isp again for image processing.
In the earlier official documentation, it was described like this.
And, I do have access to the desired features. Write my own camera driver, use dtoverlay to load the camera driver, and then use the device node /dev/video0 to read the data received by unicam.My camera comes with an internal data processing process and there is no need to use the Raspberry Pi's internal isp again for image processing.
I've found that this doesn't work on the Raspberry Pi 5. The Raspberry Pi's built-in isp becomes a required path.
I ported the driver to a Raspberry Pi 5 only to see that /dev/video0 can't be used to fetch images directly. From my observations using media-ctl, the new path is:
Code:
camera pad(/dev/v4l-subdev2)--->(pad0)csi2(pad4)--->rp1-cfe-csi2_ch0(/dev/video0)Or is the Raspberry Pi planning to ditch support for mipi cameras that are not libcamera mechanisms?
Statistics: Posted by xumm — Wed Dec 20, 2023 6:56 am
