But, as far as I can tell from the diagram on the link shared, you will boot into EL1 and not EL2. This means that you cannot run a hardware accelerated VM on KVM (via something like qemu).
This makes a Snapdragon Linux laptop not as useful. BTW Asahi Linux on Apple Silicon enters on EL2 which allows qemu+KVM.
Entering on EL1 instead of EL2 seems to be be an outstanding issue with current Snapdragon based Linux laptops too. Can anybody correct me here if I'm wrong ?
> In short, our roadmap for the next six months includes work in these areas:
> End-to-end hardware video decoding, on Firefox and Chrome
> Implementation of the libcamera-SoftISP camera solution
> GPU and CPU performance optimizations
> Power optimizations (Suspend/DCVS)
> Making our firmware openly available (in Linux-firmware)
> Access to easy installers (Ubuntu and Debian)
"Making our firmware openly available (in Linux-firmware)" is a big one. How are firmware updates currently distributed ? People using Linux Laptops probably don't want to be signing into some Qualcomm website to get latest firmware updates. Also downloading firmware updates from some random link either would not instill a lot of confidence either.
I feel these 2 big items need to be addressed before Linux on Snapdragon can be a truly attractive option.
This one?
If it's using the design that I prototyped while at Qualcomm, it's jumping to EL2 at ExitBootServices when the boot to Linux at EL2 option is enabled.
Didn't look at a release firmware yet to see what was the final impl, but was told that it did ship :)
The "linux-firmware" repo is the standard place to put it, my reading is that Qualcomm are doing this in the right way.
Indeed, Linux-firmware is the correct way to distribute. Qualcomm is currently _not_ doing this for all their Snapdragon Elite firmware (please read the linked article).
That way, you would only need to have one hub (Homey, Home Assistant, IKEA, Apple TV, etc.) and it would be able to keep all your stuff up to date and control everything via Matter. Right now, we are slowly moving towards a future where any hub can control any device, but you still need to run the vendor hub if you want firmware updates.
But Qualcomm should allow users to run accelerated aarch64 VMs on a Snapdragon Elite (just like users can on Asahi Linux).
> I think that for many use-cases containers already replaced VMs even for developers.
If you're happy with running containers then you'll be fine. However, many developers like VMs for the extra isolation they bring and other features like running a full Linux distribution. Example: You may want to run Ubuntu on your Snapdragon Elite system but also want to run a full aarch64 NixOS within a VM.
- Snapdragon X Elite (2,574 / 12,562)
- iPad M4 (3,630 / 13,060)
How fast can a system compile my projects that is.
I think it's best to wait for System76 or someone like Asus to get there.
Qualcomm is heavy on sales and marketing and all of these promises have been made before on previous silicon releases. Their management hates open-source and only permits what is absolutely necessary. I am not hopeful for the future on these devices. They will be locked down and closed source in various ways that people just don't know about yet.
I wonder if it won't be a little late when the laptops will be finally available to consumers.
(Also likely for people who don't have $$$ to throw around for hardware)
I'm hopeful that Snapdragon will offer an alternative ARM platform for laptops that can handle more than just browsing. As consumers, we need options, and the more, the merrier. I'm still undecided about the short-term success of Snapdragon. For now, I'm betting/waiting on the MacBook Air with an M4 as my daily driver, although I do prefer the Lenovo ThinkPad format.
To be fair, these might be server platforms and Chromebooks, nobody is buying ARM notebooks to run their favourite FEM package.
Qualcomm has been shipping closed-source modules for Android mobiles for years. Support of the another similar platform changes nothing. Adreno GPUs exist for many years and upstream support is deplorable. Nothing was stopping Chromebooks making ARM/Adreno support in upstream ever. Page is a marketing and not a binding. Continue to downvote all you want. Qualcomm and open source doesn't belong to the same sentence - history of the alternative ROM for Androids is a living poof.