They won't directly support it because in their view the Google Play process is a more secure way of verifying they supplied the binaries than is possible of f-droid. If reproducible builds were possible maybe there could be some mechanism to verify a given binary is built from a given commit of the source tree.
stsquad
joined 1 year ago
Btrfs never really worked out for me (I think default COW doesn't play nice with VM images) and ext4 works great.
Pretty much. From v8.0 onwards all the extra features are indicated by id flags. Stuff that is relevant to kernel mode will generally be automatically handled by the kernel patching itself on booting up and in user space some libraries will select appropriately accelerated functions when the ISA extensions are probed. There are a bunch off advisory instructions encoded in the hint space that will be effectively NOPs on older hardware but will enhance execution if run on newer hardware.
If you want to play with newer instructions have a look at QEMUs "max" CPU.
When did this change? AIUI creators got a larger cut of YouTube premium views compared to ad share.
Virt-manager isn't super scriptable but the underlying libvirt can be controlled by virsh which is a shell interface to libvirt. You can use both at the same time, e.g. start and stop via virsh and access to gui container via virt-manager/virt-viewer.
Erm...yes? There is obviously a rush to integrate the latest generative AI tools in everything without thinking about the consequences of it's failure modes.
It's called vrms (virtual RMS) and Debian at least packages it.
Isn't the GPU documented now?
https://docs.broadcom.com/doc/12358545
There are reverse engineered docs as well: https://github.com/hermanhermitage/videocoreiv
SystemReady is already a thing. When it becomes mandatory for design wins hopefully it will become more common place.
I wouldn't say that, it's just there is a lot in vendor kernels and little incentive to upstream stuff for older SoCs that have already shipped. It's true Google has come around to the importance of not drifting too far from upstream and hopefully we are starting to see the results of that change in attitude.
As I understand it my colleges in the QC landing team @ Linaro spend a lot of time getting stuff into the various upstreams.
QEMU absolutely will use hardware floating point where it can but only when it will give the correct results. FEX and Box64 are user mode emulators which achieve their speed by avoiding emulation where they can buy thunking at API boundaries.