@ljs I'm gonna say it: Lina and the whole marcan troupe use dogpile harassment tactics.
They should know better about how awful these tactics are for the targeted person, but maybe that's precisely why they use them.
@ljs I'm gonna say it: Lina and the whole marcan troupe use dogpile harassment tactics.
They should know better about how awful these tactics are for the targeted person, but maybe that's precisely why they use them.
fontconfig's source code apparently uses 4 spaces to indicate an indent of one, and a singular tab (which you then need to set to width 8) to mean an indent of 2.
@marcan
$ curl --cert-status https://alx.sh
curl: (91) No OCSP response received
Don't worry though, I'm sure your Let's Encrypt cert is safe from hijack, just ask these guys: https://notes.valdikss.org.ru/jabber.ru-mitm/
this is a lobster, you cannot convince me otherwise
@Suiseiseki the other currently required binary is DRAM initialisation. When the processor first powers on, it can only access SRAM (the CPU caches) and needs to first train the DRAM to access the entire memory. This is done by a fairly small binary that runs once at boot; if someone has the skills and time they can reverse engineer it, as they've done for earlier rockchip SoCs.
@Suiseiseki It's needed to initialise the system. However, rockchip posted source code for at least part of the ATF: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/16952
The one they released source for lacks scmi support so CPU/GPU reclocking unfortunately doesn't work with it. I don't know if a third party can add support for that.
I suspect they'll follow this up with a more complete submission when they get the time. From what I gather, rockchip's software team is feeling some pretty bad crunch in the past year or so.
Got u-boot with device tree overlays working, naturally it was a bug in the proprietary ATF that one can work around by just not passing it the device tree at all. Good stuff.
@Suiseiseki It was apparently the xf86-video-nv Xorg 2d driver, no clue how that interfaces with the kernel though, since that was a long time ago back before kernel mode setting and might not actually be touching GPL'd code even (Xorg server itself is MIT, Xorg was in charge of bashing around the hardware back then)
@alexeymin isn't this the same thing nvidia did ages ago? I vaguely recall them obfuscating their code at some point before coming up with the GPL condom.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.