Jarkko Sakkinen
jarkko
I really enjoy working on this tracker project. When I got pattern editor, I knew that it will become something. It will take at least a year to really nail every bit but it has the critical mass of getting done (eventually) :-)
Very early work on sample editor.
Very early work on sample editor.
0
0
0
Jarkko Sakkinen
jarkko
I guess I just follow the lead :D
❯ find -name json_writer.c
./tools/testing/selftests/container/json_writer.c
./tools/testing/selftests/bpf/json_writer.c
./tools/bpf/bpftool/json_writer.c
./tools/net/ynl/ynltool/json_writer.c
Maybe we should have shared json_writer.h/c for selftests?
❯ find -name json_writer.c
./tools/testing/selftests/container/json_writer.c
./tools/testing/selftests/bpf/json_writer.c
./tools/bpf/bpftool/json_writer.c
./tools/net/ynl/ynltool/json_writer.c
Maybe we should have shared json_writer.h/c for selftests?
1
0
0
Jarkko Sakkinen
jarkko
This looks "pre-done" :-)
https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/tree/include/uapi/linux/container.h?h=container
Better to distance off for a while and then revisit.
https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/tree/include/uapi/linux/container.h?h=container
Better to distance off for a while and then revisit.
0
0
0
Jarkko Sakkinen
jarkko
I thought that rather than focusing on reversing Polyend Trackers MT song format it is better to build a "DAW" that can support its features. I'd figure the lack of such program has blocked any major progress.
So there you have it I'm building a retro-modern tracker ;-)
So there you have it I'm building a retro-modern tracker ;-)
0
0
0
Jarkko Sakkinen
jarkko
Edited 3 months ago
also has polyend's 8 channel view :-) in this view text fields need some work but yeah looking pretty good
0
0
1
Jarkko Sakkinen
jarkko
As long as LLMs don't ask the questions for you, there's no problem with LLMs IMHO :-) Iterating the question is everything in engineering. Everything else is relatively nothing.
0
0
3
Jarkko Sakkinen
jarkko
After refurbishing dhowell's patch set for a while I end up to the situation where I you realize that you're chasing for solution rather than for the problem. So time to pivot.
So I'm thinking that most of it could be possibly done by adding a new feature for sys_clone() instead... Need to experiment with this. I.e., chasing for the problem now...
So I'm thinking that most of it could be possibly done by adding a new feature for sys_clone() instead... Need to experiment with this. I.e., chasing for the problem now...
0
0
0
Jarkko Sakkinen
jarkko
As per target hardware for this Polyend inspired tracker i think i target it for Raspberry Pi 4 and make sure that with that hardware it has a great user experience. I have one spare Raspberry Pi 400, which makes a great testing platform for this use and purpose.
0
0
0
Jarkko Sakkinen
jarkko
Edited 3 months ago
it's glitchy atm because heavy changes how pattern editor is rendering but getting there ;-) music courtesy of 4mat - red sector theme
0
0
0
Jarkko Sakkinen
jarkko
Moxie seems to be only person in the planet nailing login like it was 2021 :-)
Linear email-link-passkey track.
First time I witnessed this like it should be done everywhere really since five years ago.
Linear email-link-passkey track.
First time I witnessed this like it should be done everywhere really since five years ago.
0
0
0
Jarkko Sakkinen
jarkko
I'm slowly putting together a software clone slash inspired of first edition of Polyend Tracker:
https://bsky.app/profile/jarkk0.bsky.social/post/3mesd3hefkk22
All the graphics code is going throug rewrite (undoing egui for other than layouts, per-pixel rendering to texture for each block) and doing direct pipewire backend, and later on CoreAudio for macOS :-)
#polyend #chiptune
https://bsky.app/profile/jarkk0.bsky.social/post/3mesd3hefkk22
All the graphics code is going throug rewrite (undoing egui for other than layouts, per-pixel rendering to texture for each block) and doing direct pipewire backend, and later on CoreAudio for macOS :-)
#polyend #chiptune
1
0
3
Jarkko Sakkinen
jarkko
Test case naming conventions people use for kselftest when you have broad spectrum of them?
0
0
0
Jarkko Sakkinen
jarkko
The update I 'm still fine-tuning for dhowell's patch set is not just respin but is actually conceptually different.
I.e. from being task_struct centered into nsproxy centered, and repeated spawning that Eric Biedermann complained about (for legit reasons) is being addressed.
Containers are 1st class namespace now members managed by nsproxy to address the need of not wanting to use namespaces ;-)
I.e. from being task_struct centered into nsproxy centered, and repeated spawning that Eric Biedermann complained about (for legit reasons) is being addressed.
Containers are 1st class namespace now members managed by nsproxy to address the need of not wanting to use namespaces ;-)
0
0
0
Jarkko Sakkinen
jarkko
Edited 3 months ago
Getting there: https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/log/?h=container
# /usr/lib/kselftests/run_kselftest.sh -t containers:run.sh
TAP version 13
1..1
# timeout set to 45
# selftests: containers: run.sh
# create: alpha: pass
# create: beta: pass
# list/json: fetch: pass
# list/json: has alpha: pass
# list/json: has beta: pass
# list/json: has ready state: pass
# ps/json: fetch: pass
# ps/json: has alpha: pass
# ps/json: has beta: pass
# create: reject invalid name: pass
# run: no procfs without --proc: pass
# run: procfs with --proc: pass
# wait: observes termination: pass
# stop: SIGTERM exits init: pass
# stop: fails when TERM ignored: pass
# kill: SIGKILL exits init when TERM ignored: pass
# run: non-zero exit fails: pass
ok 1 selftests: containers: run.sh
# /usr/lib/kselftests/run_kselftest.sh -t containers:run.sh
TAP version 13
1..1
# timeout set to 45
# selftests: containers: run.sh
# create: alpha: pass
# create: beta: pass
# list/json: fetch: pass
# list/json: has alpha: pass
# list/json: has beta: pass
# list/json: has ready state: pass
# ps/json: fetch: pass
# ps/json: has alpha: pass
# ps/json: has beta: pass
# create: reject invalid name: pass
# run: no procfs without --proc: pass
# run: procfs with --proc: pass
# wait: observes termination: pass
# stop: SIGTERM exits init: pass
# stop: fails when TERM ignored: pass
# kill: SIGKILL exits init when TERM ignored: pass
# run: non-zero exit fails: pass
ok 1 selftests: containers: run.sh
1
0
0
Jarkko Sakkinen
jarkko
Opaque container objects can be sealed better or that can be tuned very far at least.
This has the advantage when you actually want bare metal + containers instead of bare metal + vm wrapping the containers.
I mean when you want that in *production* and don't want to worry too much of security aspects.
One example use case is to maximize the throughput in video streaming service for each node. This is the "Netflix use case" (they use FreeBSD).
This has the advantage when you actually want bare metal + containers instead of bare metal + vm wrapping the containers.
I mean when you want that in *production* and don't want to worry too much of security aspects.
One example use case is to maximize the throughput in video streaming service for each node. This is the "Netflix use case" (they use FreeBSD).
1
0
0