I got my Genesys 2 FPGA alive with an old version, and can now conclude that either OpenSBI or SM is causing the misbehavior. It is super stressing when you don't even know whether you can get something theoretically to work, and I was in that limbo for few weeks. What a relief although work is not done yet! Was not sure whether the flashed CVA6 had something wrong.
1
0
1
@billyjoebowers I actually tend to put these ShaperBox as the only mixing plugin when I first construct track in order not to be overwhelmed by choices. It has pretty much those features except AI :-) ShaperBox is more like AL plugin for me, i.e. Artificial Limitation, i.e. if I don't get something to the ballpark what it has then the sound must be wrong...
0
0
0
Jarkko Sakkinen
jarkko
is EP same as big.LITTLE with different branding? https://eclecticlight.co/2023/10/23/how-does-macos-manage-virtual-cores-on-apple-silicon/ #arm
0
0
0
@gregkh @conor Stable firmware extension to be exact. It works on a standard RISC-V CPU with MMU. It even works on my VisionFive 2 RISC-V board: https://github.com/keystone-enclave/keystone/issues/339. It is more like in the area of TrustZone than big cloud things like SGX or SEV-SNP, providing tools to implement secure boot and stuff like that. Thus, I see worth of doing this on side up because I really believe that it is a piece that RISC-V needs something like this to be successful. I'll move forward in upstreaming if it becomes official part of OpenSBI firmware.
1
0
0
Jarkko Sakkinen
repeated
repeated
Inkscape
inkscape@mastodon.artHere at the Inkscape Project, we're excited about our upcoming milestone... we're turning 20 in November! š
Watch for an opportunity to learn more about some of our contributors later in November.
For now, we're hoping to collect your best wishes and what you've achieved through using #Inkscape for sharing with our contributors and the community (open until Oct 31):
https://office.inkscape.org/nextcloud/index.php/apps/forms/s/cc5Jy4FwbkbkWqweGCkAQRTp
0
4
1
Jarkko Sakkinen
repeated
repeated
Free Software Foundation
fsf@hostux.socialProtect developer freedom. Abolish software patents. Learn why software patents are unjust by checking out the new design of our #endsoftwarepatents initiative. https://u.fsf.org/3f-
0
1
1
1
0
0
@conor ... and thus it is a non-issue for me if this cannot go to e.g. staging. The priority is to get the Keystone project use a kernel patch instead of OOT driver. While at it, it really does not hurt to ask from @gregkh if this can be picked to staging but not a thing thah I'm go to do today or tomorrow. Still because this works on standard hardware, it *does* make sense for Linux *at some point* (and open source firmware extension).
Seems much less difficult exercise than the one I had with Intel SGX in the past...
Seems much less difficult exercise than the one I had with Intel SGX in the past...
1
0
0
@conor I would like to also point out that Keystone driver is better to be a subsystem in vmlinux because it offers broader scope of applications than e.g. SGX or SEV-SNP, i.e. kernel could run payloads there and thus other subsystems could find use for it. For instance, we could possibly have backend for trusted keys and stuff like that. But for now either my korg tree or staging at most are the most appropriate...
1
0
0
@conor it is highly CPU architecture dependent feature and any TEE must be part of the boot flow so I don't think it should linkable as module at all. As part of the boot flow any possible in-kernel use cases are enabled, i.e. other subsystems could have Keystone backend. Thus, I think it is best pick for now.
1
0
0
I can request riscv-keystone@vger.kernel.org if there is broader interest on this work.
0
0
0