Live data from Hacker News

Qualcomm Linux 2.0

qualcomm.com

61–70 of 71 posts

Re: Qualcomm Linux 2.0

#61

Earlier quoted context omitted.

If you want fanless arm linux machine, why not macbook m2 air + asahi linux ?

Asahi still doesn't support a lot of basic things like: external displays, Thunderbolt, hardware accelerated video decoding, 120hz refresh rate, etc.

It supported my 175hz monitor on a M1 Mini.

Re: Qualcomm Linux 2.0

#62
post #43

Qualcomm is not a good software steward. Every time I used something they had their hand in, it was abandoned rather sooner than later. Eudora: bought, milked, killed. BREW: rotted. AllJoyn: dead. Toq/Mirasol: gone in two years. CodeAurora: shut down. And the $899 Snapdragon Dev Kit: shipped months late, then cancelled with support "paused indefinitely" while units were still in transit. Even Adreno drivers barely ge…

It has now been decades since I used Eudora. I still feel I lost the best email client due to Qualcomm’s neglect

Re: Qualcomm Linux 2.0

#64
post #43

Qualcomm is not a good software steward. Every time I used something they had their hand in, it was abandoned rather sooner than later. Eudora: bought, milked, killed. BREW: rotted. AllJoyn: dead. Toq/Mirasol: gone in two years. CodeAurora: shut down. And the $899 Snapdragon Dev Kit: shipped months late, then cancelled with support "paused indefinitely" while units were still in transit. Even Adreno drivers barely ge…

Eudora was the first email client I used in the 90s, I didn't know that qualcomm was responsible for it's disappearance. Looks like the source was released in its last breath[0]; i'm a bit surprised it hasn't been scooped up and maintained anywhere

[0] https://computerhistory.org/blog/the-eudora-email-client-sou...

Re: Qualcomm Linux 2.0

#65
post #29
post #2

And here I was hoping they'd decided to support Linux on the Snapdragon X2 chips.

When will folks learn companies only support Linux or any other FOSS to the extent their own business goals? None of them are on the game for the well being of the community or whatever. Profits and lower R&D costs, that is all.

But it benefits the community

Re: Qualcomm Linux 2.0

#66
post #39

Earlier quoted context omitted.

holy hell.. the price tags...!

why on earth would anyone buy that shit if you can buy a macbook pro that literally looks and feels like art vs. a plastic windows laptop? it used to be that Apple was the pricier option but I guess not anymore

The problem with MacBook is that they have a shit OS...

Re: Qualcomm Linux 2.0

#67
post #38

Earlier quoted context omitted.

Asahi still doesn't support a lot of basic things like: external displays, Thunderbolt, hardware accelerated video decoding, 120hz refresh rate, etc.

It supports external displays, just not on any port

I was going by Asahi's own support page: https://asahilinux.org/docs/platform/feature-support/m1/

It seems that external displays are only supported on HDMI (e.g. Mac Mini) but DP Alt mode is still listed as WIP so I'd assume MacBook's with only USB-C (all of them?) can't support an external display.

Re: Qualcomm Linux 2.0

#68
post #46
post #25

Earlier quoted context omitted.

Upstream requires a level of quality most developers cannot meet.

"Quality" is maybe overloaded. Upstream requires the code to meet their sense of taste, and some of that is about quality, and some of that is about undocumented design concepts. It's not hard to meet the quality bar. Meeting the design requirements is extremely hard.

Perhaps "maintainability" is a more suitable term?

Re: Qualcomm Linux 2.0

#69
post #45

Earlier quoted context omitted.

Why can’t upstream just take their drivers? Isn’t that the point of requiring those drivers to be GPL?

Linux tries to avoid special cases. That means that when someone shows up with a new driver that's either not something that fits into an existing category, or which sort of (but doesn't entirely) overlap with an existing driver, there's an extended set of design discussions about how to make this new driver fit into existing infrastructure in a way that's consistent with what's there and which also allows new things…

I get that. But it's a platform that is so similar to existing Linux on ARM offerings.

All the subsystems to run a laptop should already be there, no?

Re: Qualcomm Linux 2.0

#70
post #45

Earlier quoted context omitted.

Linux tries to avoid special cases. That means that when someone shows up with a new driver that's either not something that fits into an existing category, or which sort of (but doesn't entirely) overlap with an existing driver, there's an extended set of design discussions about how to make this new driver fit into existing infrastructure in a way that's consistent with what's there and which also allows new things…

I get that. But it's a platform that is so similar to existing Linux on ARM offerings. All the subsystems to run a laptop should already be there, no?

ARM isn't consistent in the way that the x86 platform is. Each vendor's SoC usually requires specific support.
Post reply on HN