ssc377qe fpv: drop the prebuilt imx335 module (#139)
This overlay carried a 25KB sensor_imx335_mipi.ko because the driver OpenIPC built at the time could not reach the rates this board needs: its 2560x1920@60 mode served 30fps and its 90fps mode produced no usable output at all. The blob shadowed the built module and fixed it for this one device, and for nobody else. The source behind it is now what OpenIPC builds. openipc/sensors carries it as sigmastar/infinity6c/sensor_imx335_mipi.c instead of a symlink to the infinity6e driver (OpenIPC/sensors#3), and the infinity6c loader states the lane count it needs (OpenIPC/firmware#2343). sigmastar-osdrv-sensors is unpinned, and this device's defconfig already selects it -- BR2_PACKAGE_SIGMASTAR_OSDRV_INFINITY6C selects BR2_PACKAGE_SIGMASTAR_OSDRV_SENSORS -- so the module is built and installed to /lib/modules/5.10.61/sigmastar either way. The overlay copy was only ever shadowing it. Removing it means this device tracks the driver instead of freezing a copy of it, which is the point: the next person who needs a mode changed can change it. The built driver is a later revision than the blob (72ad30b against the 30fdac4 it came from) and measures the same or better on an SSC377QE, rebooting before every mode: 2592x1944@59 59.2 fps (blob 59.2) 2560x1920@60 60.1 fps (blob 58.4) 2208x1248@90 89.5 fps (blob 89.5) 1920x1080@120 116.1 fps (blob 119.6) Verified end to end on hardware afterwards: with the built module and the merged loader and nothing else, the loader applies lane_num=4 on its own and a 60fps request delivers 60.0. Nothing else in the overlay changes.
This commit is contained in:
Reference in New Issue
Block a user