after quitting consumer social media i found this site again: https://thedailywtf.com/articles/totally-valid

... Finland making to the EBU finals ;-)

Windows NT guy here supporting Windows95Man in #eurovision #esc2024

Co-authored an update from the @MastodonEngineering team with my friend @renchap - a sneak peek at what is coming in 4.3 (and looking ahead from there). We'll aim to make these updates a regular feature for the blog. Let us know what you think! #MastodonAPI #SpreadMastodon https://blog.joinmastodon.org/2024/05/trunk-tidbits-april-2024/

@aks @doskel +1

@AmpBenzScientist @lupyuen thanks will check it!

And neither I'm against AI, I'm critical towards the business practices and fair use. It is not very intellectual take sides on tech itself but more like how it is applied and controlled.

No need to be perfect. I've quit everything that I don't actually need for anything.

IMHO, good way to protest against bully business practices of AI: exit the most consumer oriented social media. I think it was good time finally quit Facebook fully given the trends. I'm not perfect. I.e. I have still some commercial social media like Slack, Youtube and BlueSky but at least the most heated stuff is gone, or I never was there anyway.

E.g. I think I continue to build my career without LinkedIn, and find the jobs that fit me better through traditional methods of job finding (talking to friends, getting contacted by friend, sending queries and the usual). It is time to go #offtheradar :-)

gym week #3

The Kernel Report - Jonathan Corbet (@corbet), @LWN

The recording of this recent talk is now available on the #ossna2024 schedule page: https://ossna2024.sched.com/event/1aBNs/the-kernel-report-jonathan-corbet-lwnnet

Slides can be found here: https://static.lwn.net/talks/2024/kr-ossna.pdf

Direct link to the recording: https://www.youtube.com/watch?v=DAqjl_x4hZc

#Linux #kernel #LinuxKernel

Browsing without account:

• #Instagram: https://imginn.com/
• #Twitter / #X: https://nitter.poast.org/

@lupyuen You can do memory protection also with RISC-V without MMU by configuring so called Physical Memory Protection (PMP) registers in M-mode and running applications in U-mode. So it is memory protection based on physical memory partitioning instead of virtual memory. RISC-V would be a good platform for product low-cost but still quite secure products.

EDIT: Oops, meant to write U-mode, S-mode is one that exists when there is an MMU :-)

@lupyuen I have one SBC for RISC-V (VisionFive2) but would be nice to get one MMUless SBC too (i.e. without S-mode). I.e. kind of RISC-V "arduino".

@liskin @ljs @vbabka do not want to sound like boomer but people should neither "fan" linux nor rust or anything like that. inspiration should come from hardware, domain and stuff like that. they are translatable from kernel to kernel and from language to language, and that is what matter in the end.

@edwintorok @sdbbp right thanks for to great answers! i mean mostly hlt and similar are used to conserve energy (e.g. in PM an similar), and e.g. locks just reschedule so i could imagine that in e.g. linux nop should not cause any actual collateral damage.

i'm just used to specs where opcode does one and only one thing :-)

I wish there was USB-stick that would send one single key press when the button is pressed. That's all it would do.

@liskin @ljs @vbabka doing symbian was not all that bad.

i was not in the UI layer. i was in the team doing audio subsystem, which contained resource manager, DSP codecs, audio policy etc. e.g. setting up the correct codecs, managing memory for audio, opening correct streams depending on phone state (like incoming call when you have video playback ongoing).

i also learned basics of ARM CPU's at the time, which is obviously still useful knowledge, JTAG debugging with Lauterbach TRACE32 and stuff like that. so even tho symbian is a relic, all the skills are still useful and can be applied :-) that way i got into middleware and operating systems.

when i started in 2003 symbian phones were larger and had two ARM CPU's separated by a physical bus: the first was for the phone OS and second one was for the application OS (symbian). when series 60 3.0 came along around 2004 the hardware architecture moved into one CPU model and to a real-time kernel called EKA2, which hosted the whole symbian in one of its threads.

One thing that was tedious was the edit-compile-run cycle. If I had to fix a bug, it took about 45-60 minutes to run it on a device, as both compilation and flashing took a while.

Doing e.g. Linux kernel is not that hard if you've worked in any possible operating systems before because in the end it is all about understanding hardware and the domain where you are working and the source code's layout is just like a different legislation and policies in a foreign country.

OK, so WFI on RISC-V is not detemistic! It can be same as HLT (x86) or WAIT (ARM) but could also be nop 🤷 Beyond me tbh. #riscv

@ljs if nokia clash had happened maybe few months later i might be living in canada and maybe still working for blackberry, and developing webkit ;-) i'm a kernel dev by accident (sort of).