Stories
Slash Boxes
Comments

SoylentNews is people

Linux 5.6 Is The Most Exciting Kernel In Years With So Many New Features

posted by Fnord666 on Monday February 10 2020, @07:18PM   Printer-friendly
from the lots-of-new-and-shiny dept.

spiraldancing writes:

www.phoronix.com

This kernel is simply huge: there is so many new and improved features with this particular release that it's mind-boggling. I'm having difficulty remembering such a time a kernel release was so large.

The quick summary of Linux 5.6 changes include: WireGuard, USB4, open-source NVIDIA RTX 2000 series support, AMD Pollock enablement, lots of new hardware support, a lot of file-system / storage work, multi-path TCP bits are finally going mainline, Year 2038 work beginning to wrap-up for 32-bit systems, the new AMD TEE driver for tapping the Secure Processor, the first signs of AMD Zen 3, better AMD Zen/Zen2 thermal and power reporting under Linux, at long last having an in-kernel SATA drive temperature for HWMON, and a lot of other kernel infrastructure improvements.

Original Submission

 
This discussion has been archived. No new comments can be posted.
Linux 5.6 Is The Most Exciting Kernel In Years With So Many New Features | Log In/Create an Account | Top | 93 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by DannyB on Tuesday February 11 2020, @02:40PM (3 children)

    by DannyB (5839) Subscriber Badge on Tuesday February 11 2020, @02:40PM (#956840) Journal

    Maybe another alternative . . .

    Maybe it is time that Kernel developers consider the possibility of . . . OMG . . . having a standard kernel driver API. Not for all possible kernel modules, but for device drivers. It seems device drivers are the vast majority of kernel source code, or so I am under the impression. If necessary later, introduce a 2nd improved kernel driver API. Surely enough is understood about what kernel access a device driver needs after about 30 years?

    Another idea, multiple standard interfaces for different kinds of drivers. Eg, filesystems. Direct memory access drivers. Video devices. Etc. A single driver could implement one or more of these interfaces.

    --
    The lower I set my standards the more accomplishments I have.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 0) by Anonymous Coward on Wednesday February 12 2020, @02:52AM (2 children)

    by Anonymous Coward on Wednesday February 12 2020, @02:52AM (#957063)

    You think you want a stable kernel interface, but you really do not, and you don’t even know it.

    from the executive summary of https://www.kernel.org/doc/html/v4.14/process/stable-api-nonsense.html [kernel.org]