Live data from Hacker News

Linux 7.2

igalia.com

41–50 of 141 posts

Re: Linux 7.2

#41

Why is DRM being implemented in the Kernel; What is the profile for an end-user who wants this in their FOSS?

People who want to play video games, or watch videos using hardware decoding, or train machine learning models? DRM here means https://en.wikipedia.org/wiki/Direct_Rendering_Manager

> DRM exposes an API that user-space programs can use to send commands and data to the GPU and perform operations such as configuring the mode setting of the display.

> User-space programs can use the DRM API to command the GPU to do hardware-accelerated 3D rendering and video decoding, as well as GPGPU computing.

Re: Linux 7.2

#43

Earlier quoted context omitted.

That doesn't help when the monitors don't have DP2.1 support.

I havent seen a monitor (besides tvs) that has HDMI2.1 but not DP2.1

I can tell you mine does: a Corsair XENEON 27QHD240. Or the somewhat popular and badly named Acer Nitro XV275K P5biipruzx

I'd say it's usual for displays released in the 2-5 years old range. HDMI 2.1 got somewhat quick monitor support for consoles, but search for "first DP2.1 monitor" gets results from 2024

Re: Linux 7.2

#47

Who is the main audience for this type of content? Genuinely curious because I am not a serious Linux user. What type of info do you get out of this for those who read this? So i can glance your insight?

As a long time desktop and server user, why do I look at changelogs...

New filesystems and major changes to existing ones (large performance improvements, new features like adding better compression standards which I now know I can use, fixes to long-standing bugs which open new use cases).

New protocols like wireguard when it was new and exciting (still is now that I think of it). When that was mainlined, I knew I had some network rearchitecting to do.

New device drivers like amdgpu when it was massive news. Less so these days since most hardware is well supported, and I don't buy the absolute latest.

New kernel APIs which I can use in my programs — like landlock, when it was merged I knew it was time to improve sandboxing in some of my stuff.

Though LWN and kernel newbies do it best, already linked by others.

Re: Linux 7.2

#48
post #19
post #17

Earlier quoted context omitted.

IIRC, a non-AMD contributor was working on adding HDMI 2.1 support to Linux's AMD driver, and then AMD managed to get the HDMI Forum to see that their position was moot and was making things very awkward for AMD.

Oh this makes sense! Obviously, it can't be illegal for a non-forum-member to add HDMI support; it's just an HDMI forum policy after all, not law. That's certainly the link I was missing for this to make sense.

presumably someone at Valve said "either you do this or we will pay an open source contributor 100k a year to reimplement every spec you make for the rest of time"

Re: Linux 7.2

#49
post #20

Okay, so ELI 5 why I would now use HDMI instead of DP? All my monitors support DP, my GPU has more ports for DP ... I am genuinely interested as I've never even considered using HDMI for my Desktop.

Because your motherboard only supports HDMI. The last three I used had HDMI, and sometimes VGA.

Re: Linux 7.2

#50
post #7
post #5

Earlier quoted context omitted.

It's a well-formatted changelog of the most salient features of the release. Linus doesn't provide one apart from a list of added commits and merged branches, which isn't very useful unless you are a kernel developer.

This isn't quite right. This is a well-formatted changelog of the changes that Igalia has contributed to the release, AFAICT. KernelNewbies publishes a much more general summary of changes (it is much longer than this one). https://kernelnewbies.org/LinuxChanges https://kernelnewbies.org/LinuxVersions

What great resource thank you !

This new thing is pretty cool :

    =USB4STREAM for streaming data with USB4=

    In addition to Thunderbolt networking, which was already supported, this release adds support for streaming data directly over a cable as well (USB4STREAM). It is very simple and basically just transfers raw packets from one host to another. The driver exposes /dev/tbstreamX devices on each side of the link that can be used to transfer data using regular filesystem operations such as read(2) and write(2):

    host1 # cat /dev/tbstream0
    host2 # echo hello > /dev/tbstream0

    This can be useful in cases where network tooling is not available or just for existing applications like dd and cat that do not support sockets. This feature can be used at the same time with thunderbolt_net so they don't rule each other out, and it allows multiple streams to be created.
Post reply on HN