Mainly from discussions with me, and only run as 32 bit.
I'm assuming you're referring to https://github.com/anholt/drm-v4l2-test
, which came about from https://github.com/anholt/linux/issues/ ... -240482532
Gavinmc42 wrote:His V3D driver is being used in Gentoo64 and Fedora64 for Pi3's.
So this driver compiles in 64bit mode which probably mean the v4l2 will too?
There is an issue with MMAL and IL in that they pass user pointers in a u32 struct to the VPU as a callback cookie. That obviously fails in a 64 bit world and needs some magic shim. The problem then becomes that you can't tell if the app has been compiled as 32 or 64 bit, and therefore which variant of the structure is being passed in.
IIRC The V4L2 camera driver uses internal cookie values and lookups and therefore should be OK. Codecs should be coming online soon via V4L2 and so should hopefully also work on 64 bit.
I think there is something called Unicam?
Quick google found this
Even if raw data only was working it could be useful in Aarch64 and use the NEON stuff for image processing.
Start looking in the latest/next kernel source?
Unicam is the CSI2 receiver peripheral. Nearly there in our kernel https://github.com/raspberrypi/linux/pull/2513
(I got hacked off with the upstreaming process but it should get ressurrected as time allows).
64 bit is not a priority at Pi Towers, therefore it's still really being driven by those in the community that care.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.