Why does the boot-chain matter? Can't we just have a custom U-Boot implementation that interacts with the bespoke boot chain while providing standard UEFI support to the rest of the system? Isn't that how Asahi works?
A full-featured U-Boot implementation would be fine IMO. But for the generations that I've used, that's not on the table. What we get is a proprietary flow through a proprietary hypervisor into a fork of Android's bootloader (even if vanilla Linux is the target OS). There's no way to control startup boot options, and no way to use KVM, Xen or any hypervisor except the proprietary one that's also part of the boot chain.
This doesn't lend itself to flexible products, or to products that are easy for a company to design or support. That is why things like this happen: https://news.ycombinator.com/item?id=46008156
Go all in or go home, qualcomm.
Nowadays the standards for Linux support are much higher. This isn't the 1990s anymore. Releasing a half-assed support that will be obsolete in six months is pretty much useless.
Also, the fact that the drivers have not been upstreamed tells me they're most likely sub-par in terms of code quality and possibly stability.
What's the point of buying hardware whose softwares support is already deteriorating ?
Nowadays the entire thing until you land in EL1 needs to be signed by Qualcomm as well. This is without "Secure Boot" enabled. OEMs only get to run code under the hypervisor. And you might want to use a part of the hardware but someone decided the VM your code runs in shouldn't have access to that, too bad.
EL2 is still locked down for the chip this post is about, AFAIK. And everything else is is staying locked.
Lots of this is customer dependent but what you say is true for the typical android phone config that most use
It will be interesting to see what Google got from Qualcomm for the new Chromebooks (EL3 isn't even the highest level anymore, that's TME now).
The new AL BSP target for Hamoa, which is what's going to ship on the new Android laptops, runs KVM at EL2 instead of Gunyah. But it has (at least partially) Qualcomm-owned EL3.
This is much better than that. Not great yet, but much better than that in comparison.
I agree Qualcomm's support of open source is better, while still leaving a lot to be desired.
That said, though, Apple can't be best for embedded applications, they're plainly not competing in that space - or can you make e.g. a custom ticket vending machine with an Apple chip?
Gunyah is disappearing from new chips, slowly but surely.
X2 doesn't have it anymore, the IoT range has it as optional now. And it's going to be deployed less from there
Who benefits from having separate BUs maintain fully separate software stacks? It's duplicated, wasted effort on Qualcomm's part. Maybe it lets them double-charge their customers for this duplicate effort, but that feels short-sighted. And there's certainly no benefit in delivered software quality.
Qualcomm should be making it easy for everybody to buy and use their chips, not artificially segmenting every single customer. They could sweep the market so hard if they were just a little less greedy.
The drivers might be up on LKML, but they're not mainlined yet. And this is just gen5. It would be great if you could fix your gen4 and 4.5 drivers, so that people building products with your chips weren't stuck on an orphaned vendor kernel.
Also your boot-chain is still closed and proprietary, and completely different than the one used by all other ARM vendors.
And don't even get me started on Gunyah and GearVM, or on the proprietary, locked nature of your BSP, or how far behind TI and NXP the quality is. Maybe also consider releasing some actual documentation on your chips.
I know multiple developers who have sworn off Qualcomm and will never design with their chips again at any price point. Your closed-off support model is 100% the culprit, and it hurts your core business.