straw man. no one is "worried" except you
Considering I use MacOS 15.8, bootcamp into Windows 10 for gaming, and nowadays my only linuxes are on my NAS (DSM 7.3) and 2 VMs, one with TAILS and one with Kali, I am not worried in the slightest about what happens with Canonical...
about the volume of work, they should be using LTS or SLTS kernels, instead of bespoke Kernels. For instance, Ubuntu 26.04 LTS uses kernel 7.0 (not LTS, and certainly not SLTS), which means canonical engineers have to do all the backporting and patching work...
Anywho. Good luck to canonical and their users.
I used F-droid on my Blackberry Q10, and KeyOne, But I used so few apps from there, and all of them were on the official playstore, so, at the end, for my Razr+ 2024, I did not bother to install F-droid.
Still, glad to see the team moving forward, I desire them good luck, and have nothing but gratitude towards them.
Why is this something new? Isn't it just an ARM chip, and Linux has been running on ARM for ages? And I think Android still uses the Linux kernel, no?
Is all the other bibs and bobs that hang of the chip. Mem controller, GPU, NPU, USB controller, networking, wireless, the works
Since I live In Venezuela, Qualcomm does not want me to read the blog post.
So, I have a question for those who have read it, as TFS does not say:
The Qualcomm integration work is fully FOSS drivers? Or is a bunch of closed source drivers and binary BLOBs.
I do not care one way or the other, as I am more pragmatic than ideological in that regard. But I do know that with Closed source Linux drivers:
1.) In the tail end of the life of the hardware, support becomes spotty, as newer kernels stop supporting the closed drivers.
2.) Oftentimes the reverse engineered FOSS drivers lack certain features and lag in performance the closed source counterparts (nVIDIA drivers, and old AMD* drivers come to mind as prime examples).
3.) Certain important projects ARE ideologically minded and flat out reject any closed source drivers and BLOBs, so that restricts the projects one can approach (of the top of my head OpenWRT, but that is not relevant to Snapdragon X2).
I hope Qualcomm becomes "good Linux Citizens" and go "full FOSS drivers and firmware" like Intel and AMD, but I wanted to make sure.
* One example dear to my heart, FOSS AMD drivers for the Xpress200 chipset in modern kernels lack support for the s-video out, that propiertary drivers have. And an old kernel/distro will not do, as the use case was connecting a latop to the net so that an old CRT TV could display youtube and other net content. Don't ask
After all, everything eventually evolves into crabs.
And yet "Crab People" is one of the few things to which "Simpsons already did it" does not apply
Crab People!
Everybody panic!!!!!
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3F...
Perhaps slightly tangential to topic, but while we are discussing the merits of what could be summarised as a quick - but sucessful - movie project using an old idea, the UK has just shown 70 Up, which is the latest and final release of a documentary following the lives of 14 people from age 7 to 70.
Simpsons already did it.
Given the pitance we pay in Venezuela for the tickets (something like U$D 6 for 2 tickets), this wil barely register in the "profitability" part, but, at least, is two more butts on seats for the stats.
Could have seen it in streaming later on (is not like this needs a big screen, or has some art-sy quality), but I wanted to show support in the only way I could.
is that 6 months out of the year you can operate the datacenter without Aircon.
Imagine the energy savings.
All previous versions of the Linux kernel are available. Nothing stops any distro project from freezing the version they include. In fact, this has been done many times before, since modern Linux is a "bloated piece of crap" (TM) for some people's purposes.
Oh, wait, is even worse, because LTS and SLTS kernels will receive AI patches. You will have to fork the last Non-AI kernel, and develop all the patches yourself, without ever again looking at the Linux mainline code, as some of that may have AI patches in it... Also, if you want that kernel to suuport new hardware, you will have to write the changes yourself...
Good luck with that.
All previous versions of the Linux kernel are available. Nothing stops any distro project from freezing the version they include. In fact, this has been done many times before, since modern Linux is a "bloated piece of crap" (TM) for some people's purposes.
Tell us how that works for your favourite "non-AI" distro in 2040, when the last non-AI SLTS Kernel (6.12) has been going without any patches for 4 years.
3... 2... 1...
they did it with the books, why not CDs, SA-CDs and DVD-Audio?
The GCC folks have obviously a far better understanding of the problem than the Debian leadership.
"For the time being, the GNU Compiler Collection (GCC) policy is to decline any legally significant contributions which include LLM-generated content or are derived from LLM-generated content. "
Linus Torvals and Greg K-H are using AI in the Linux Kernel and introducing LLM generated code in the Kernel (mostly pathces) NOW.
I'd venture the guess that the Kernel is "Legally Significant" from Debian's point of view.
What is Debian to do if the adopt the same approach as GCC? Reject the Linux Kernel due to the presence of AI code?
Tha's a bold plan you propose...
Will be a sleeper build, I already have a case from 2015 at the ready. And of course, no RGB
"No problem is so formidable that you can't walk away from it." -- C. Schulz
