if it is an official repo then why it is not in the list of official repos listed on their website? https://www.raspberrypi.org/github/
pointed to by Raspberry Pi Foundation employees whenever someone asks them what the official repo is.
the word of employees isn't the word of the company. To be official it needs to be on material published under the company name/domain/logo like the website, the documentation, and so on. It's appalling that I need to explain this, but here we are.
Stintel was dead wrong multiple times with his statements that the repo is not official. It IS official.
They already have. In their official repo, with a license attached.
That repo is as official as it gets
the argument here is that some people think this repo isn't official, answering with "yes it is official" or variations thereof is not a valid rebuttal.
I've already stated multiple times why upstreaming to linux-firmware is undesirable
From what I understand, (ignoring the "fk broadcomm" PM thing, as all raspberry pis so far have been merged regardless of this person's opinion) the main requirement here is that the repo gets some form of official recognition (i.e. it goes in the main website in the place I mentioned above, for starters) or they move that repo under their officially recognized github organization, here https://github.com/orgs/raspberrypi/repositories?page=1
You literally also said yourself you don't like having to use that repo
No, I never said such a thing.
Well you did, but OK, you didn't say that because you kinda know that "works for raspi foundation and is a mod in their forums means nothing", but just because it's annoying to maintain a patched tree.
go flash an offficial OS image and find me one BCM43455 or BCM43456 blob that cannot be traced back to that repository.
How do you define "trace it back" to that repository? Yes hashes are the same but that just means someone has taken the same files and hosted them somewhere. I can git clone that repo and re-upload it as mine, does not mean I can re-license their binaries as GPLv2.
You mean you see the source of their build system pulling files from it? That would be better than nothing (better than the git committer's email for the very least) but it is still kind of weak evidence.
prove it by providing the URL of the "alternative" official repo from which the official images distributed on their official website are pulling their files.
Not sure why you assume they must be in a public repo.
What about internal shared folders or internal repositories? Because in a lot of embedded devices the firmware blobs can be extracted by the firmware (obviously) but there is no repo anywhere for them, and they are not in the GPL code drops (also obviously).
You clearly don't work in corporate America. I do.
raspi foundation is in the UK, and even then, I've seen my share of random stuff getting posted or bundled with source drops then retconned a while later when legal finds out what has actually happened and scrambles to protect the company's IP