Well, much modern neuroscience research does need neuroscientists to understand quite a bit about how modern computer hardware works (or doesn’t), if they don’t want to screw up their data collection. Some of it can be offloaded on people like myself, writing high quality software and providing some knowledge on demand, but that requires actually funding people like myself by contributing financially to the software. The widespread lack of understanding of the complexities involved in modern computer hardware, operating systems etc. probably also contributes to the lack of actual support for projects like Psychtoolbox, following the false logic of “I don’t know anything about this, but how hard could it really be?”. Or people without deep knowledge write their own software, hence so many toolkits with shiny websites, trendy programming languages, maybe even the occasional nice GUI (because all these are relatively easy, or easier to learn to do), but shockingly bad implementations in the lower-level parts that actually matter for reliable and precise data collection and which require deep understanding of the hardware and the internals of modern operating systems.
Mostly because much of that hdmi_timings stuff in the RPi’s config.txt file is legacy Broadcom firmware proprietary stuff, only workable with their proprietary and limited fkms interface, whereas Device Tree Overlays are the standard way of doing things for the ARM world for fixed/semi-fixed hardware, or quite often in general on SoC’s, so that’s what standard Linux device drivers like the kms video driver use.
Yes, that’s what i’ve hinted at / would have helped stepping you through for paid support.
My opinion is that this should be paid for by your lab / PI / out of overhead grant money for your project, or similar, not out of your own pocket, given that 150 Euros / year are nothing for most funded labs in industrialized countries.
Anyway, glad you could solve it and learned something useful for the future about the RPi in the process.
-mario