popcornmix

@acidtech `initial_turbo=10` should give you the benefit of faster booting without the downside of force_turbo. It will just force turbo for the first 10 seconds.

force_turbo=1 only sets warranty bit if used with over_voltage. And only on some Pi models (not Pi4). There should be no increase in chance of corrupting sdcard with initial_turbo (or...

Setting ``initial_turbo`` or using a faster sdcard are the obvious ways of speeding it up. Connecting a uart and enabling bootloader and/or firmware logging may provide some information about what...

The 32-bit kernel can decompress itself, so is stored compressed on sdcard. The 64-bit kernel doesn't support that so it is a larger file and takes longer to load from...

>Possibly something to do with the EDID in your particular monitor, and the way that (AIUI) the EDID gets parsed differently in the 32-bit (by firmware-code) and 64-bit (by userland-code)...

> Has this set the over voltage warranty bit? (The project uses force_turbo=1 but doesn't use overvoltage settings) No, you need an explicit `over_voltage` settings (plus `force_turbo=1`) to set the...

I believe the `O_SYNC` in `open("/dev/mem", O_RDWR | O_SYNC)` means the mmap will be uncached by arm, so no flushing is required.

No immediate idea. I should point out that we are moving toward the kms driver being default (so 3d driver running on the arm) which is incompatible with this API...

Just to confirm, you tested with an empty config.txt (so not even ``dtoverlay=vc4-fkms-v3d``) and it still failed on Pi4?

It stops "auto" boosts, caused by running gpu jobs that require higher clocks (high resolution/framerate hardware video decode, encode, deinterlace). The core clock will still change as arm frequency changes...