Intel-Linux-Processor-Microcode-Data-Files VS score

https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/main/releasenote.md looks like they released a new microcode (24000024) affecting these units on Feb 14th this year.

Package: intel-microcode Version: 3.20221108.1 Priority: optional Section: non-free/admin Maintainer: Henrique de Moraes Holschuh Installed-Size: 6460 kB Depends: iucode-tool (>= 1.0) Recommends: initramfs-tools (>= 0.113~) Conflicts: microcode.ctl (<< 0.18~0) Homepage: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files Tag: hardware::TODO, role::app-data, use::driver Download-Size: 4509 kB APT-Sources: http://deb.debian.org/debian testing/non-free amd64 Packages Description: Processor microcode firmware for Intel CPUs

They have been sort of cracked, but it doesn't matter. The web or chain of trust of those updates from the vendor to the processor is what matters. They're at least CRC checked to prevent loading corrupt files.

https://ieeeaccess.ieee.org/featured-articles/reverseenginee...

https://github.com/intel/Intel-Linux-Processor-Microcode-Dat...

https://github.com/platomav/CPUMicrocodes

Not to “well aktchually”, but all modern processors do have regularly updated microcode that’s uploaded at boot time - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files

6-94-3 would become 6-5E-3. https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/6c0c4691e5bb446e0e428ebca595164709c59586/intel-ucode/06-5e-03

OpenBSD kernel has no support for loading microcode on AMD CPUs, A number of issues/errata on AMD systems may be fixed as part of AGESA updates, in addition to microcode as part of BIOS/firmware updates. While there have been microcode updates released for Zen+ or newer CPUs, but these seem to be less frequent than Intel.

Is it anymore of a "magic incantation" than the linux-image-XYZ package which controls which OS kernel is installed?

If you want to see when Intel issues new microcode updates, it is all available on their GitHub: https://github.com/intel/Intel-Linux-Processor-Microcode-Dat...

https://ossia.io uses widgets and qgraphicsscene for the main UI rendering and Qt rhi for the GPU pipeline, and it's performing well enough for our use-cases - I was working on it on a 1080p screen on a Pi4 recently and it certainly felt much much faster and responsive than chrome on the same hardware.

I use it for live c++ recompilation in https://ossia.io - all the code is in there. https://github.com/ossia/score/tree/master/src/plugins/score-plugin-jit/JitCpp

> I feel like visual programming gets a bad rap because of things like this. As an electronic engineer that used to love LabView and life long user of NI Reaktor and Max/MSP, those tools are fantastic if you don’t approach them with an imperative programming mindset.

aha, in the long run I ended up making https://ossia.io which is as VPL as it can get. Yet it still embeds a LOT of textual languages.

For me both VSCode and CLion lag heavily.. whenver I tried CLion it was completely unuseable on my project https://ossia.io which is only 500kloc (and I try to try it pretty much once a year since it was in beta)

https://ossia.io does some of it, I've been working on a new release that also supports the whole QtQuick stack in the node graph items but you can already combine videos & shader effects

In https://ossia.io with PCH, using clang, ninja, mold, and some artificial split in shared libraries for development builds, I get a compile-edit-run cycle of a couple seconds in general... I wouldn't say it's too much of a problem if you use the tools already available

If you're interested in multimedia https://ossia.io is always looking for new contributors!

Tools like Ossia Score, Chataigne and PureData (pd) can also help a ton in building interactive art and triggering other A/V software.

here's a simple example of how to do it in https://ossia.io score : https://streamable.com/wkklek