This is awesome. I would love if you had some examples on how to use AntMedia as a source. I am mostly in video engineering so the read the source comes slower to me. This would be really handy in many cases.
What bugs me most about this stuff is the dishonestly.
This is about AdBlockers.
It's okay to say it's bad for your business and you don't want them. To make up all these other excuses is what is painful and just feels so patronizing.
Search engines have shown over and over that they'll talk all the money but hide behind the 'we're just the market' cover when one of their ads serves you with a virus.
It may not actually be OK to say that, since admitting it publicly could make antitrust regulators jobs easier when investigating how Google uses its stranglehold over the browser and search markets to enforce its stranglehold over the online advertising market.
There should be extra (and enormous) antitrust penalties for publicly lying. These lies can be proven with internal communications gained from discovery or from leaks (incentivized by large bounties).
It's both imo. The security issue is both true and a huge problem being actively exploited on a massive scale. Its a "Ah great, we can improve security _and_ cripple ad blockers" moment for Google.
Can you imagine if documentation like this was available for modern hardware?!
Even something "open" like the raspberry pi doesn't have this level of detail available. The process of deep but accessible technical documentation appears to be a lost art.
You're just using the wrong part. If you get an STM32 or NXP iMX, there are tens of thousands of pages of TRM available to describe the function of every block inside the SoC. The core iMX7 technical document is over 7,000 pages.
You won't get everything, especially anything ARM has licensed out to the chipmakers like the CPU/NVIC/AHB, but it's a lot deeper than you probably need.
i.MX isn't perfect, like there are still closed-source microcode blobs for things like SPI DMA, but it's better than nothing. You can at least build it into a design without having to worry that the supply of boards is being strangled.
They don't share schematics. They don't share source code. They barely tell you anything about the custom chip(s) they're now putting in the raspi for GPIO and ethernet/USB. You can't buy them. Hell, they've used custom SoCs made for them by broadcom for years now, which they have exclusive access to.
The only "openness" that the raspi foundation engages in is upstreaming of drivers into the mainline kernel and into mesa, which is ultimately self-serving in the end. It reduces the burden on their end of carrying patches for their kernel and ensures other linux distros also pick up some of the slack supporting their products.
As for those broadcom chips? get used to it. All modern hardware of any reasonable capability has all the docs sealed behind NDAs that you have to buy a LOT of chips to even get offered. Even then you're expected to take the package deal that the silicon vendor hands you and not invent anything yourself. Chipmakers offer "full ecosystem solutions," not general-purpose parts.
The artist of the music released "wanderers" another short film from Erik Wernquist without voice and just the music. Maybe he'll do the same for 1 rpm?
https://youtu.be/pIubYfm-YO0
