![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
SystemReady is already a thing. When it becomes mandatory for design wins hopefully it will become more common place.
FLOSS virtualization hacker, occasional brewer
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.
It really depends how you see the firmware boundary. You can either treat it as a set of magic numbers you load onto the hardware so it works or see it as an intrinsically programmable part of your system that you should be able to see the source code for or live without support for the device.
I run Circe in Emacs because it’s lightweight and integrates with the modeline for not overly distracting notifications.
If the system is SystemReady then the EFI boot chain is fairly straightforward now. My current workstation just booted off the Debian usb installer like any other pc.
It’s a web of trust. If the package maintainer is doing due diligence they should at least be aware how the upstream community runs. If it’s a one person passion project then it’s probably possible to give the changelog and diffstata once over because things don’t change that fast. Otherwise they are relying on the upstream not shipping broken stuff.
I just installed Ubuntu for my 11 year old and they could use it fine. Didn’t bother with any parental controls on the device itself (although I can ssh in if needed) because the network deals with filtering at a DNS level.
I wonder which of the many fetch tools support 24bit terminal colours.
That’s what the reflog is for!
You can launch Minecraft Bedrock with the mcpelauncher of the Steam Deck or you can use Waydroid.
Sorry I was referring to: https://mcpelauncher.readthedocs.io/en/latest/
This is the way 😉 although the Minecraft launcher is pretty good these days running under Waydroid is considerably less hacky as it’s not having to thunk between android and Linux userspace.
Yes it does. You can derive the domain from snooping DNS lookups but the URL is part of the encrypted get header.
An interesting piece but isn’t this what VC investors do, not every play will result in a unicorn and those that do pay for the losses of those that don’t. I expect more than a few billion will evaporate into vapourware as we crest this wave of generative ai hype.
Don’t be too hard on Collin. Looking back on the threads it’s fairly clear he’s been the victim of a social engineering attack on an overworked maintainer. People were pressuring him to hand over maintainership while expressing disappointment at the slow pace of development. The off-list contact by Jia must have seemed like a helpful enthusiastic solution to a burnt out developer.
Well the account is focused on one particular project which makes sense if you expect to get burned at some point and don’t want all your other exploits to be detected. It looks like there was a second sock puppet account involved in the original attack vector support code.
We should certainly audit other projects for similar changes from other psudoanonymous accounts.
It’s looking more like a long game to compromise an upstream.
Time to audit all their contributions although it looks like they mostly contribute to xz. I guess we’ll have to wait for comments from the rest of the team or if the whole org needs to be considered comprimised.
Microsoft has been working with a number of open source projects for some time now. It shouldn’t be that surprising anymore.
Isn’t the GPU documented now?
https://docs.broadcom.com/doc/12358545
There are reverse engineered docs as well: https://github.com/hermanhermitage/videocoreiv