Tootfinder

Ok so the first boss fight of the STM32MP2 bringup (getting the A35s running at full speed with caches) is over.
The second isn't going so hot. I've configured all of the documented SYSCFG and COMBOPHY registers (I think). It's not linking up, is in DState 4 whatever that means, and I'm not seeing any change on the tx/rx lines when i do this.
Which means one of two things. Either the register settings I've done are wrong (possible, I'll double check)...

Studies showing that "AI" isn't creating the productivity gains that "AI" boosters promised are important but I think that they sadly don't help us win as much as some believe. We're winning at the wrong game:
https://tante.cc/2026/01/25/winning-the-wrong-g…

Winning the wrong game
With studies upon studies showing that actual measurable productivity gains through “AI” (which these days basically means chatbots) are really hard to come by and that “workslop” (meaning the extra work created for the rest of the organization by one person using “AI” lowering their work quality) eats up a lot of what might have […]

I'm building webkit-gtk right now. It's one of these messy packages where a few source files need a lot of memory to compile, and ninja can randomly order jobs so that all of them suddenly start compiling simultaneously. So to keep things going smoothly without OOM-ing, I've been dynamically adjusting the available job count via steve the #jobserver.
While doing that, I've noticed that ninja isn't taking new jobs immediately after I increased the job count. So I've started debugging steve, and couldn't find out anything wrong with it. Finally, I've looked into ninja and realized how lazy their code is.
So, there are two main approaches to acquiring job tokens. Either you do blocking reads, and therefore wait for a token to become available, or you use polling to get noticed when it becomes available. Ninja instead does non-blocking reads, and if there are no more tokens available… it waits till one of its own jobs finish.
This roughly means that as other processes release tokens, ninja won't take them until one of its own jobs finish. And if ninja didn't manage to acquire any job tokens to begin with, it is just running a single process via implicit slot, and that process finishing provides it with the only chance to acquire additional tokens. So realistically speaking, as long as there are other build jobs running in parallel, ninja is going to need to be incredibly lucky to ever get a job token, since all other processes will grab the available tokens immediately.
This isn't something that steve can fix.
#Gentoo #NinjaBuild

"If “AI” is actually more expensive than paying actual people actual wages that’s still a good investment for capital because it is about breaking up the structures, networks and organizations that help workers organize and fight for labor standards and fairer wages."
(Original title: Winning the wrong game)
https://

Winning the wrong game
With studies upon studies showing that actual measurable productivity gains through “AI” (which these days basically means chatbots) are really hard to come by and that “workslop” (meaning the extra work created for the rest of the organization by one person using “AI” lowering their work quality) eats up a lot of what might have […]

Good examples in that article for why a prompt-based system for system administration seems odd: You type a hundred-word question and are told by the AI to use apt when the Fedora system doesn’t use that package manager at all. https://mstdn.social/@osnews/115702679695335298

"IBM owns Red Hat which in turn runs Fedora, the popular desktop Linux distribution. Sadly, shit rolls downhill, so we’re starting to see some worrying signs that Fedora is going to be used a means to push “AI”."
(Original title: Using “AI” to manage your Fedora system seems like a really bad idea)