Notices by Marcin Juszkiewicz 🙃 (hrw@society.oftrolls.com)

Git submodules are handy way to share files between projects.

At same time they are PITA when it comes to updating.

`git submodule update`?
`git submodule update -f`?
`git submodule sync`?

I am starting to consider dropping submodule in favour of manual cherry-picking update between repos.

@simontatham it made we wonder did anyone wrote Vim plugin for analysis of TTU files.

ViTTU would sound nice for a name. And would fit cause cursing while analysing is so common practise.

@gregkh

That post reminds me many moments in Arm architecture history...

Creation of armhf to have all distros target the same armv7.

Creation of Linaro and work done by people there.

SBSA, BSA specifications which tries to define aarch64 hardware and firmware interfaces.

Work done on making enterprise Linux distros running on aarch64 servers.

I hope that RISE will not follow aarch64 mistakes.

@jessew I would rather expect Unix introduction saying 'Linux-like' ;D

There are moments when I want to report a bug and then look at project's bug tracker and decide not to.

When there are hundreds/thousands of open bugs then what is a point of adding yet another one?

Digged through already opened one, found same shit I wanted to report filled 5 years ago. Without any comments.

Sometimes filling bugs makes no sense. And no, this is not a project where I can help with fixes.

#fosdem is coming. Survival post reminder time then.

https://marcin.juszkiewicz.com.pl/2019/10/15/how-to-survive-fosdem/

So far no one suggested changes this year.

@geerlingguy I heard that RISC-V is not ready for users yet.

But didn't thought that 360p youtube video will be too much for it. I do not remember did I ever saw so slow AArch64 system.

Twenty years old ppc32 chips can do it...

I like people's optimism when it comes to "Arm inside" laptops.

Like this post by Avi Alkalay: https://avi.alkalay.net/2024/08/intel-inside-not.html

I would like to be able to share that optimism. But no one makes Arm laptops which "just work" with Linux.

My daughter uses 3rd x86-64 laptop. All running Fedora Linux (same installation moved between drives). I would like to give her Arm laptop running Fedora Linux. Without "this port does not work, that one also not, Wi-Fi sucks" sticker on top.

@aral yes. The problem is you. And the problem is in Wayland and rest of stack.

Bitching the project does not help. Look are there solutions, do someone is working on screen reader for Wayland environment.

Help them with testing as it looks like you know how it should work.

@aral

It helps to look from project perspective sometimes.

When all you get is complaints then (as a developer) you may consider abandoning the project and work on something else.

Or when you have some work in progress but whole feedback is "it sucks".

Be constructive. Help rather just be an asshole.

Several websites write that snapdragon X devices are the first laptop with Arm cpu.

Acorn A4 was the first laptop with ARM cpu.

In June 1992. 32 years ago.

https://www.computinghistory.org.uk/det/22807/Acorn-A4-Laptop/

Thinkpad x13s session.

Some things work, bugs are present, no firmware parts, no calibration data, UEFI implementation sucks, random reboots, no video acceleration.

Feels like SBC with a screen.

@feld Yep, hardware limit as card knows how to handle standard TCP/IP packages but not much else.

Will check tomorrow after rebooting to OpenWRT.

QEMU Advent Calendar is back!

Each day will bring something interesting to run in emulation.

https://qemu-advent-calendar.org/2023/

Furniture stores use props everywhere.

It is first time when I see Fedora Linux on such prop.

RISC-V is entering some serious desktop space!

64 cpu cores, up to 128GB of DDR4 ram, 5 SATA, 2 NVME, several PCI Express slots, USB 3, 2 2.5GbE ports.

1200 USD means I will not buy one, but I am also not (yet) interested in having RISC-V system at home.

https://www.crowdsupply.com/milkv/milk-v-pioneer