• @dan@upvote.au
    link
    fedilink
    908 months ago

    A lot of Linux drivers are like this - just one or two people maintaining them. They usually eventually mainline the driver rather than having a separate Git repo though.

    • @0x4E4F@lemmy.dbzer0.comOP
      link
      fedilink
      50
      edit-2
      8 months ago

      It’s mind boggling just thinking that things like this depend on the effort of one or two guys… while on the other hand, it’s not so uncommon that a team of engineers and developers fails to deliver a working (mostly) bugfree product.

      I think management is who is responsible for the shitty decisions, as always… and, in general, just holding the team back.

      • @dan@upvote.au
        link
        fedilink
        12
        edit-2
        8 months ago

        The thing with drivers is that the hardware they’re written for doesn’t really change. A particular network card is always going to behave the same way. Once the driver works well, it’s pretty much complete, and the only changes that are needed are bug fixes, updates to handle new firmware, or adjustments if the kernel changes some implementation detail of how drivers are used. There could be months or years between updates to the driver.

        Some manufacturers have great first-party Linux support. Intel is a good example - they contribute a lot of code to the kernel, and their drivers are maintained by employees.

        • @0x4E4F@lemmy.dbzer0.comOP
          link
          fedilink
          3
          edit-2
          8 months ago

          There could be months or years between updates to the driver.

          Yes, but someone still has to implement that “a thing or two” in it every few years.

          Some manufacturers have great first-party Linux support. Intel is a good example - they contribute a lot of code to the kernel, and their drivers are maintained by employees.

          Agreed. But, to be honest, most aren’t. Just take a look at Realtek. There’s bound to be at least one chip made by them on your board (in most cases, two, LAN and audio, two very crucial pieces of hardware).

          • @dan@upvote.au
            link
            fedilink
            18 months ago

            Realtek NICs are junk (even the buggy Intel I225-v chip is better) so I try to avoid them, but I honestly haven’t ever checked which sound chip my motherboard uses. I’ll have to check if it’s a Realtek one. Realtek is generally the lower-end manufacturer for cheaper products.

            • @0x4E4F@lemmy.dbzer0.comOP
              link
              fedilink
              1
              edit-2
              8 months ago

              Realtek is basically on every retail motherboard manufacturer. Gigabyte, Asus, MSI, Biostar, ASRock, etc. If you’re talking about hi-end or server grade motherboards, yeah, but let’s face it, the chips are cheap so they’re practically in every household.

              • @dan@upvote.au
                link
                fedilink
                1
                edit-2
                8 months ago

                I’ve got a “ASUS ROG Strix B550-F” which wasn’t exactly a high-end motherboard when I got it (I got it because it was cheap), but it’s got an Intel chip rather than a Realtek one. The lower-end motherboards have Realtek NICs but I usually don’t get the cheapest of anything since there’s usually a pretty big difference in quality if you spend just a little bit more.

                The Intel I226-V chip on that motherboard is only $2.87 each (for quantities of 1000, even cheaper for large bulk orders) and the manufacturer can likely use the same PHY chip and timing components, so it doesn’t really increase the price a lot to use a non-Realtek chip.