![](/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.
For range it doesn’t add much in most cases. But it also depends on how long between journeys you have. If you’re traveling in a van and you are going to be stationary for a few weeks at a time then it can start to make sense, maybe with an extra fold out.
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 understand why all the things that require accelerators are so expensive but what the hell are red diamonds? Surely anything not carbon in the matrix would make them less diamond like?
I run Circe in Emacs because it’s lightweight and integrates with the modeline for not overly distracting notifications.
You can, they are called canals. Look at the Nile delta and the network of irrigation trenches used to spread water from the river to the wider areas. There are a number of dam projects in Africa which are all about managing water flows.
The principle problem is when your divert water it’s usually at a cost to another area that was using it.
I’ve just lugged an Ampere AVA to a conference for a demo. It’s a nice beefy machine and I think will finally be able to be a daily driver once I get it back home.
Self hosting takes time and energy and most open source developers join projects because they are interested in the project not becoming admins. On top of that building a CI system is an expensive undertaking when a lot of hosting solutions provide a fair amount of compute for free to qualifying projects.
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’m not sure if that is the op or Lemmy cropping stuff. I’ve seen similar when I’ve tried to post stuff.
I’m just getting to the end of the Dragonborn DLC before returning to continue my first run through Skyrim.
I don’t think Kamikaze’s came about until much later in the war. I’m sure a few heavily damaged planes went down taking targets with them though.
I tried all sorts of port forwarding tricks to get wireguard working on the VM that runs my HA instance to no avail. The trailscale solution works really well. The only real problem I had was magic DNS conflicts with DNS66 on my phone (which I use for ad blocking). In the end I just used a hardwired VPN IP for my HA connection.
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.
Slowly the hold outs are realising open source drivers are here to stay. I don’t think propriety divers are ever going to go away but now you can have a fully open stack for all the main GPU stacks out there. I suspect more designs are insisting on open drivers and Nvidia doesn’t want to be ruled out at the start.
Isn’t the GPU documented now?
https://docs.broadcom.com/doc/12358545
There are reverse engineered docs as well: https://github.com/hermanhermitage/videocoreiv