rotwang wrote:While I'm about it, could someone also think about posting a COMPLETE list of config.txt parameters, broken down by firmware version, and keeping it up to date, since I don't think random mentions in replies to post are a good way to document things.
There is pretty good list here:
https://www.raspberrypi.org/documentati ... fig-txt.md
And for device tree specific settings:
https://www.raspberrypi.org/documentati ... ce-tree.md
It doesn't necessarily make sense to document every config.txt setting.
Many are debug settings and would only make sense to be tried when I suggest it when troubleshooting a specific problem.
Some have been added and have never been used. For example a change is made to how the edid is interpreted.
The new scheme means we handle the HDMI specs better, but there is always a danger of regression.
So I add a config.txt setting to allow the change to be reverted, under my guidance if there is a reported bug.
But, it turns out no regressions emerge. The config.txt setting will eventually be dropped.
There are some settings that will almost certainly make the Pi work less well for almost everyone.
A danger of documenting these is users may try it, not spot the problem it causes immediately and forget about it. Weeks later they complain that something doesn't work.
It also means finding the genuinely useful settings gets more difficult (needle in a haystack).