When it comes to non-free firmware I think there's two reasonable positions - treat it like non-free code running on a remote system (suboptimal, outside the scope of current free software priorities) or treat it like software running on the primary CPU (all code on the local system should be free software, no matter where it's running). I think the FSF's position is unreasonable: https://mjg59.dreamwidth.org/70895.html
@mjg59 Fun anecdote: A friend of mine once tried to get a certain piece of open hardware RYF-certified. At the time Linux would run on the hardware, without free GPU acceleration. The shipping software/firmware did not include any nonfree components.
They rejected it because users could hypothetically install nonfree GPU drivers. They said if he could get the GPU permanently fused off, they'd certify it.
It was never certified. A few years later, free GPU drivers were available. Had he followed the FSF's ridiculous demand, users would have owned an intentionally crippled piece of hardware and lost the ability to have free GPU acceleration in the future, once it existed.
@marcan @mjg59 That...seems really backwards. I like the idea of "free software" firmware, but going scorched earth on anything that doesn't fall under a particular definition just bothers the hell out of me. I can totally see not offering support out of the box, but forcing it to be hard-disabled "in case" just means that the user now...can't do what they want with the hardware they bought.