OK, something probably pretty basic with #QEMU I need to ask.

I have this command-line, which is generated by #Keystone #RISCV #TEE build:

/home/jarkkojs/work/keystone/qemu/build/riscv64-softmmu/qemu-system-riscv64 \
   $DEBUG \
   -m 2G \
   -nographic \
   -machine virt,rom=/home/jarkkojs/work/keystone/build/bootrom.build/bootrom.bin \
   -bios /home/jarkkojs/work/keystone/build/sm.build/platform/generic/firmware/fw_payload.bin \
    \
   -netdev user,id=net0,net=192.168.100.1/24,dhcpstart=192.168.100.128,hostfwd=tcp::${HOST_PORT}-:22 \
   -device virtio-net-device,netdev=net0 \
   -device virtio-rng-pci \
   -smp $SMP

QEMU has support for #Spike, which is #CVA6 emulation.

So when I do to the above command-line simply s/virt,/spike,/g, I get this error:

$ build/scripts/run-qemu.sh
**** Running QEMU SSH on port 3617 ****
qemu-system-riscv64: Property 'spike-machine.rom' not found

How do I end up to this error message? Why does it seek a filename like that? Without rom= I can run Spike emulation but I need that bootrom for the application.

#Aalto managementin vaalitentissä paistaa ehkä eniten #demokratian:n vastaisuus, koska käsittääkseni näitä sisältöjä voi katsoa vain #X-tunnuksella. Seuraavaksi luennot instaan tai tiktokiin?

#Debian carries old 0.7.2 version of #neovim (even trixie), and neovim does not provide #arm64 (aka #aarch64) builds. This worked well for getting up-to-date nvim binary: https://github.com/matsuu/neovim-aarch64-appimage. I used #podman aliased as #docker.

I've used the one for #Linux #kernel for years but apparently there is also #LXR hosting from #Bootlin for #QEMU: https://elixir.bootlin.com/qemu/latest/source

aihetta sen kummemmin tuntematta niin tajunnunvirtahorinasta syyttely twitterissä on jotenkin metatasolla ironisuuden huipentuma, kuten myös "en ole lukenut väitöskirjaa, mutta...". https://www.iltalehti.fi/kotimaa/a/a5edc628-90e1-45fc-a7b0-0c7d763995b3

ordered a pile of #UART TTL #USB converters. out of stash, and they tend to break down :-) i need one to get serial console to #VisionFive2 RISC-V board. #riscv

en #politiikka'a hirveästi seuraile, mutta onhan tämä täysin todellisuudesta iralllaan olevaa paskaa, kun pikemminkin tänne pitäisi houkutella ihmisiä töihin. enpä taida seurailla jatkossakaan, koska masennus iski heti. https://www.hs.fi/paakirjoitukset/art-2000009944529.html

I'm trying to get #Keystone #SM ongoing with #CVA6 but stuck with SM's trap handler giving me illegal instruction. I wonder how interpret these values for #mideleg and #medeleg: https://github.com/keystone-enclave/keystone/issues/374#issuecomment-1777032123 #riscv #opensbi

I wish I had one of those #UDOO #BOLT boards so I could test #TPM and trusted keys better with #AMD #hardware. #linux #kernel

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

#pikvm is great :-)

Here 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

Protect 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-

debugging issue with #SBI. i’m a newbie on this so just found out that you can inject traces with sbi_printf(). not sure but i guess you also have to have CONFIG_HVC_RISCV_SBI=y set in #kernel? #linux #riscv #sbi

I’ve opened up #development #git tree for in-kernel #Keystone #enclave #driver:

https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-riscv-keystone.git/

Existing branches:

• keystone: follows Linus’ tree.
• keystone-5.19.y: I’m actively trying to get Genesys2 FPGA hosting CVA6 working with this kernel version. Buddy allocator works but the use of dma_alloc_coherent() to allocate contiguous physical memory for enclaves freezes the system when it is being used (not in the call itself).

Keystone enclaves are applications hosted by Keystone security monitor running inside #OpenSBI, and partitioned and protected by physical memory protection (usually shortened as PMP) machine registers.

PMP is part of standard RISC-V ISA, which means that Keystone enclaves are usable with any RISC-V CPU with MMU. There is nothing that would prevent this coming eventually a mainline feature because it works for without non-standard or proprietary components involved.

Another favorable element of having Keystone enclaves as kernel feature is that Keystones enclave can run both in U-mode and S-mode meaning that kernel subsystems could use the feature too (if wanted). For instance, #Intel #SGX can host only ring-3 enclaves, which limits its scope.

#linux #kernel #riscv #cva6

The only #diagram tool that I've ever liked was #xfig and I would still use over anything else available if it was brought to modern day.

#sublime #merge, software that I'm happy that I've paid for. There's some pretty decent fee options such as #Gitg from #Gnome but this has just tiny bit of extra comfort and performance (UI has very low-
latency).

Wrote myself a cheat sheet on how to get #unprivileged #Nix up and running because had forgotten how to do it. I like my Nix this way, i.e. a #container tool for me that actually makes sense to me I guess, and fits for my needs.

https://publish.obsidian.md/jarkko/Nix+Home+Manager

#Bitwig hack: you can get audio feedback path inside grid with "Long Delay" and "Mixer" devices.. Apparently Long Delay device can be routed back to an input of a Mixer device. Without it or with any other device this seems to not be possible.

testing #sonicware #8bitwarps sequencer and looper, recorded directly and no post-processing #musicproduction