Together with bookworm release, there's been significant changes in parameters (newer) config.txt handles, versus legacy one (ref e33ec88 #2952 (comment)).

For those using other distributions than PiOS, but still updating core firmware files (bootcode.bin, *.elf, *.dat), there is no documented clear-cut from which file(s) release points / commit hash the boundary is set between new/legacy config.txt handling: this makes necessary config.txt changes very unclear.

It would really be helpful to have such boundary documented in both config.txt documentation pages (new/legacy) , beyond simple reference to bookworm (i.e. a commit hash reference in rpi-firmware repo ?).

@lurch Thanks for consideration.