Announcement

Collapse
No announcement yet.

Linux 5.5 Required More Deblobbing Than Usual For GNU Linux-libre 5.5

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux 5.5 Required More Deblobbing Than Usual For GNU Linux-libre 5.5

    Phoronix: Linux 5.5 Required More Deblobbing Than Usual For GNU Linux-libre 5.5

    Fresh off the Linux 5.5 release, the Free Software Foundation Latin America crew has debuted their GNU Linux-libre 5.5 downstream that continues to be focused on deblobbing the kernel of drivers requiring proprietary firmware and stripping out other code/functionality that is contingent upon non-free software bits and removing the ability to load closed-source kernel modules...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Maybe WireGuard will be almost ready for being mainlined in Linux 6.0 Linux 7.0...

    Comment


    • #3
      Wow, and I thought Devuan is a waste of time. And then comes this...

      Comment


      • #4
        Originally posted by anarki2 View Post
        Wow, and I thought Devuan is a waste of time. And then comes this...
        I guess you don't mind the Orvellian future we're in. I'm glad someone is taking the time to do this. Even looking at the list is infuriating. NONE OF THOSE NEED THE MICROCODE BLOBS!

        Comment


        • #5
          Originally posted by anarki2 View Post
          Wow, and I thought Devuan is a waste of time. And then comes this...
          Youngsters around here thinking that Linux-libre is some new phenomenon. Kernels going back to 2.6 are available in the FSF Latin America archives.

          Comment


          • #6
            Is a Linux kernelwithout those binary blobs worth any time investigating?

            In my experience, when a Linux kernel doesn't have those binary blobs to load for support of hardware that require it, that hardware either doesn't work or has limited functionality.

            Comment


            • #7
              Originally posted by anarki2 View Post
              Wow, and I thought Devuan is a waste of time. And then comes this...
              OK kid

              Comment


              • #8
                Originally posted by anarki2 View Post
                Wow, and I thought Devuan is a waste of time. And then comes this...
                Do you really consider the fight for real freedom a waste of time ?
                If many fights for freedom haven't took place in the past, you would've been probably a slave in chains today.
                Just because it's software it doesn't mean that it's not important.
                One day the Linux kernel will power self driving cars and robots.
                Would you trust them with binary blobs ?
                Have you seen the "I, Robot" movie?
                Just wait until these technologies are more widespread and then you'll see how important is to have free and open source software running on them.

                Comment


                • #9
                  Originally posted by Danny3 View Post
                  Do you really consider the fight for real freedom a waste of time ?
                  Do you really consider writing a makefile or bash script to remove blobs from the kernel a fight for real freedom?

                  Comment


                  • #10
                    AFAIK it was through similar actions that the firmware loading mechanisms were implemented/improved within the linux kernel.

                    This should allow people to make improvements where certain specific firmware features are eventually taken out of the blob control and this is useful as then you will have knowledge of how the hardware works. (It was also why free software initially became necessary - to make a printer work.)

                    A problem with android is that it is too reliant on firmware blobs and patches that are not mainlined (so a slightly different issue). That means people are stuck on ancient 3,.x series kernels for much of the hardware.

                    I hope there is a day that the mainline kernel can support modern mobile hardware natively.

                    Comment

                    Working...
                    X