Reminder: the CfP for LSS-NA is open until March 15th.

RE: https://social.kernel.org/objects/b4dcda9a-582c-4803-9d6a-30e42dfc8538

Old school file browsing experience :-) Rendered as a single GLSL shader program (except top and bottom bar). There's now 1:1 correspondence between shader programs and screens. Most importantly this stabilizes latency for each tick in audio playback (smaller CPU time variance).

#tracker #polyend #chiptune

Yep, I started a C rewrite of my tracker so first version was a PoC.

I.e. want to spare time from clocks even from compiler injected memory checks. I.e. I drop Rust because of memory safety tbh. And also have really good touch what opcodes get generated.

This came up when my friend asked could this in theory to G3/G4 PPC that was basically it :-) I can do so much more now to make it compact, nice and fast.
🤷

@timojyrinki thanks! would be anyhow good to learn the debian process, appreciate this, thank you!

I wonder if I should get this packaged: https://codeberg.org/jarkko/lsiommu

In addition of /sys traversal it discovers through libudev. I should probably make this dynamic option and change CONFIG_DISCOVERY to CONFIG_UDEV (i.e. /sys or /sys + udev).

It did not exist in easy single executable form so I did this already long time ago.

You can filter out the info also with lspci but it is tedious/unergonomic :-)

@timojyrinki, How do I do first babysteps to package this for Debian?

I once made a chatbot with it mixing some basic algorithms to derive text randomly and put it to bunch of random Telegram channels. It was not great idea :D It really caused some havoc. So up for next project :D

Just for plain interest how to make ollama running in NVIDIA GPU useful for something? Not for being LLM prompt. Just ideas what would be applications :-) Like, could I make it analyze local network traffic for instance or be part of that type of scheme?

@jani, I guess I did not learn anything from previous round ;-)

I'll create a rootns AUR repository for Arch Linux kernel with rootns patches. I want to run it in my desktop for some time to get more feel for it and fix any glitches.

I think it is pretty good but for a namespace it is better to try to use it for a while before submitting anything.

The idea of rootns is to namespace root / superblock i.e., that way this dilates from David Howell's original series (or by evolution actually following all review comments from Al and Eric). In David's series topologically container object was something managed by task_struct. In this series, rootns is part of nsproxy, and purely a namespace.

You would think that root is part of filesystem namsepace but actually formally filesystem namespace is all non-empty sets of mount trees not including empty state (there's BUG_ON() to underline this in VFS code). This namespace plays only with detached roots and that way can give guarantees of not mixing up the kernel state.

Once again (as with swcam driver), I ripped off the SRCU/spinlock locking scheme from SGX driver and there are no loops inside spinlock or anything weird like that. I should remember to add cond_resched()'s tho to iterations :-)

I think the gist of David's code had absolutely a reason to exist. It was just not enough constrained, scoped and explained. And it was completely misunderstood by most. I have to give credit to Eric Biedermann giving such great (and many) review comments despite being in existential opposition. This is uncommon and shows high-standards professionalism in a person.

Super useful tidbit on serum wavetables (44 kHz vs 48 khz): https://backstage.polyend.com/t/workflow-making-wavetables-on-tracker/4742

Making a tracker feels more and more like implementing interpreter. Probably a good first class optimization would be to have some kind of JIT the pattern data. And you do get stuck into infinite loops because of misinterpretation of note delays, jumps etc. And all that must be considered both in context of looping a pattern or playing a song.

Would be nice if there was also external bootlin toolchains for LLVM.

E.g., if you want to compile bpftrace to a BuildRoot image. Most of the time when compiling image is spent on LLVM compilation.

A tracker is essentially a interpreter where each instruction within thresholds (low and high) takes the same amount of time.

for a kernel developer this type of user space software is particularly interesting to do given the real-time feedback of user interface and audio and how everything needs to tick correctly. you need to think rt threads, memlocking, threading model and everything. i do enjoy working on it.

minimum criteria is to have at least a few tracks done from start to end using only my software

pattern editor might make it seem that my tracker is almost done but actually it will take ages to polish it and do all the details right (at least a year) :-)

and as long as i have vision what is not right open sourcing it right now would only add stress. i publish it once i don't know what to do with it :-)

My mind says my tracker is good as it is in Rust but my heart says "rewrite it in C, you want to do it Jarkko, let's make it small and tight just the way you want it, together".

Can't resist... the force is too strong... :-)

The first version of loader/saver for Polyend's MT project files and MTP pattern files done :-) PTI instruments were already. Scaffolding done also for wavetable and granular synthesis...

https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/tree/include/uapi/linux/rootns.h?h=rootns

Documentation of internals will follow to kernel/rootns.c and make htmldocs works too (Documentation/ is generated from DOC-comments).

Lo behold rootns: https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/log/?h=rootns

#linux #kernel #container