For the remaining part up until end of 09/2024 at the university I’m working on enabling stuff in https://sochub.fi/, which is IMHO remarkable being academia driven project.
#SoCHub produces yearly a new bigger RISC-V chip with IP blocks from the partner companies for the purpose different topics where you need a #SoC. If I got it right, they are also beefiest SoC’s designed by #academia anywhere in the world.
#Tampere #University drives the project and integrates the IP blocks to the chip design with their own in-house developed 500 kSLOC tool, partners provide the IP blocks around RISC-V core and eventually they can be used for applied research.
For 10/2024 I’m probably looking for a stable corporate job after windy 2022 in a startup, and this period at the university but plans are then pretty much wide and open.
not going to cover this, i just used it as a reference to create a nu-discoish’s bass sound. also quite happy with the guitar made with @uheplugins #zebra2. i’m going to use these sounds to make a track for a compilation coming from a new israel based freeform #psytrance (or #suomisaundi as it is called) record label. ps. neither autotune nor any pitch correction in the vocal, recorded from laptop mic :-) #audio #musicproduction
@ljs @jani @vbabka I’m trying to convince David (Howells) that we should seed Rust support to keyutils because it is exactly the context where Rust would work out pretty well. It would also provide governance from forks. I’m already putting together patches for this, even tho have not checked yet what David responded in IRC to this idea.
Other benefit is to be able to deprecate old rusty bash based test suite. With that change we could start using something like rstest to build up more comprehensive test suite. Also Rust test suite is easier to deploy to a BuildRoot image to run kernel tests.
These bash/autotools test suites are terrible for any SoC type of stuff tbh. They should be IMHO deprecated in almost any possible project… They also add up to the security risks because less test suite is run, more likely bugs will leak in. The only nicely aged test suite I know is kselftest which packages easily to anywhere :-) It’s not perfect but we should be happy that we have it…
I’m not excited about oreboot. Fork is not engineering. Neither is replacing mature field-stressed implementation with immature Rust implementation.
Enabling Rust on side with C in upstream #coreboot would be engineering. This way upstream stays mature but Rust can be used to further improve the implementation.
EDIT: I gave this more thought and here’s what I spammed :-) To put story short I don’t believe this works as a “standalone product” but is still potentially useful: https://social.kernel.org/notice/AdIOdilzP66IevvbCy