DPI interlace:
It will be in the next release, but you can try it now using either the unstable branch or "rpi-update" (usual caveats!)
- If you want H/V Sync, just use "dtoverlay=vc4-kms-dpi-generic" and append "dtparam=interlaced" to your desired video parameters.
- If you want Composite Sync, do not map GPIO1 to DPI -- you'll need an overlay that uses one of the "_gpio2" pinouts. Then you'll need to run some user code to generate CSync on GPIO1 using PIO. This is the simplest option for monochrome.
VEC over GPIO:
It's never been tried -- but AFAIK it ought to work -- change this line to add VIDEO_OUT_CFG_SEL_PAD_MUX_BITS and use an overlay to assign pins 4-11 to DPI. Sorry, can't offer any more detailed support for this non-standard use case right now.
It will be in the next release, but you can try it now using either the unstable branch or "rpi-update" (usual caveats!)
- If you want H/V Sync, just use "dtoverlay=vc4-kms-dpi-generic" and append "dtparam=interlaced" to your desired video parameters.
- If you want Composite Sync, do not map GPIO1 to DPI -- you'll need an overlay that uses one of the "_gpio2" pinouts. Then you'll need to run some user code to generate CSync on GPIO1 using PIO. This is the simplest option for monochrome.
VEC over GPIO:
It's never been tried -- but AFAIK it ought to work -- change this line to add VIDEO_OUT_CFG_SEL_PAD_MUX_BITS and use an overlay to assign pins 4-11 to DPI. Sorry, can't offer any more detailed support for this non-standard use case right now.
Statistics: Posted by njh — Mon Feb 10, 2025 11:20 am