Kernel: Stable Branch, New Release, and Mesa Size
-
EasyOS Kernel 5.10.77 compiled with wireguard vpn and broadwell snd
-
Proposed Patches Would Let Linux GPU Drivers More Easily Know When User Input Occurs - Phoronix
Proposed Linux kernel patches by a Google engineer -- based on existing functionality found within Android and Chrome OS kernel builds -- would allow Linux's DRM display/GPU drivers to more easily know when system input events occur.
Why should the Linux Direct Rendering Manager drivers be looking out for user-initiated input events? Ultimately it's about speculatively trying to reduce latency. If the system has been idle but an input event just occurred, chances are there will be text or a portion of the rendered display changing.
-
Linux 5.16's Staging Enjoys An Autumn Cleaning - 20k+ Lines Of Code Removed - Phoronix
There isn't any shiny new drivers part of the kernel's staging area for Linux 5.16 but exciting from a maintenance perspective is a rather healthy clean-up affecting multiple areas of this "proving grounds" area of the kernel.
While no big additions for staging in Linux 5.16, there are multiple clean-ups to different staging components that yielded a lot of code removed. In fact, over 20k lines of code were removed from the staging area for Linux 5.16.
-
Apple M1 PCIe Driver Leads The PCI Changes For Linux 5.16 - Phoronix
Sent in on Friday by Bjorn Helgaas were all of the PCI subsystem updates for the Linux 5.16 merge window.
Arguably most notable with the PCI feature pull request is the introduction of the Apple Silicon PCIe driver. That Apple PCIe driver written by Alyssa Rosenzweig and Marc Zyngier is to get more components working for the Apple M1 MacBook and Mac Mini systems. Besides PCI Express itself being important, getting this driver mainlined is necessary for being able to get USB Type-A, Ethernet, WiFi, and Bluetooth working on the Apple M1 hardware.
-
Mesa package much bigger than it needs to be
Furthermore, those two groups are only different by 25 bytes.
I could post-process the mesa package and convert the two groups into symlinks. So instead of 11 files occupying 139MB, there would be just 2 files occupying 26MB. The size difference is staggering!
Today I decided to try and find out how this has come about in the first place. Well, it seems that the mesa developers are incredibly stupid: they create these drivers as hardlinked files. However, hardlinked files cannot be copied across filesystems, they become separate files. The mesa project has done this right from the start, which I find extraordinary.
Do they have some good reason to do this? Are they in fact not stupid? Have I misunderstood something?
- Login or register to post comments
- Printer-friendly version
- 4502 reads
- PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is releasedAfter three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. |
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future TechThe metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. |
today's howtos
|
Recent comments
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago