1. 1

    Wow, that’s quite a vague title :)

    Fun fact: drm_auth stuff was causing some strange bugs in the FreeBSD port of amdgpu a couple years ago. (Most of which somehow went away by upgrading to 5.0, and the other bug was solved by using xwayland 1.20.) So I’m happy to see any DRM_AUTH removals.

    BTW, why are you checking the “authored” option when posting anything from the collabora blog no matter the author?

    1. 1

      I was indeed a bit hesitant about the title, but ended up leaving is as is lol. As for the “authored”, I manage the Collabora blog! :)

    1. 2

      That site does not contain audio.

      1. 1

        Oh sorry, didn’t see it as meaning there was actually audio. Will update!

      1. 1

        Could I use this to route audio across the network with SSH?

        1. 2

          Could I use this to route audio across the network with SSH?

          Network audio is not in the scope of PipeWire, for now.

          1. 1

            thanks for the answer!

        1. 1

          I have mixed feelings about Docker-based solutions like cross. On one hand when they work, that’s nice.

          But when it doesn’t work out of the box (e.g. cross breaks Cargo workspaces), you’re left with nothing. Rust has no real documentation on how to do cross-compile without cross. All existing guides are like the “how to draw an Owl” meme: “add --target and then solve all other problems yourself.”

          1. 1

            Totally agree. I’d also say that this is a sad state of affairs because rust is so obviously well suited for embedded systems. Its like a match made in heaven really. The way they set up the HAL is such a good plan. I would LOVE to be able to just cross compile easily without all the setup.

            1. 1

              @kornel Rust does have documentation : https://github.com/japaric/rust-cross

              1. 1

                Thank you!

            1. 5

              Kernel development has always been highly distributed. What has that to do with COVID-19 or is that just click-bait?

              1. 9

                Some projects, such as Chrome, have slowed their release cycles.

                Distribution is not necessarily a fix to the problem. People can still get infected, suddenly have kids and partners at home. And these are just the reasons when you are lucky. We should not forget that we are in a global pandemic where people die, so grieving and similar are part of the mix.

                So, I guess it’s fair to highlight that.

                1. 2

                  That’s correct. I was simply highlighting that despite the many challenges presented by COVID-19, (infectons, lockdown, kids at home, crazy schedule adjustments, etc), Linux kernel development continued.