Linux 6.13 Staging Clears Out 107k Lines Of Code From Old & Unmaintained Drivers

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Weasel
    Senior Member
    • Feb 2017
    • 4498

    #41
    Originally posted by DanL View Post
    WTH do you think I was talking about in my example?


    Some kernel versions don't require any updates at all. The driver I used has had about 10 commits in the last 5 years, and most of those aren't updates for newer kernels. You and avis make it sound like every driver needs to be completely rewritten for every kernel release. Nice try though..
    Original point was about 3rd party drivers' manufacturers not working and not available on Linux.

    Your argument/reply to it was something like "That's not fault of ABI break that's fault of the manufacturer!!!"

    Which is complete bullshit because the reason they won't write drivers for Linux is because they have to keep maintaining it on every fucking kernel release ever.

    Were we talking about drivers that don't need updates? No.

    Comment

    • back2未來
      Phoronix Member
      • Oct 2023
      • 78

      #42
      [ What changed for a driver's codebase within a certain amount of time? and can customers/users maintain a needed hw driver by themselves, if easy enough (and if out-of-tree)?
      How about managing firmware for abandoned previous in-tree driver code?
      Are there even complaints for this time staging/unmaintained code clearing (are these summarized?)?

      Would it be sufficient having a repository for previous in-tree driver code and compatible firmware (probably a pretty static repository, if not, os recognizes demand for support)? (thx) ]
      Last edited by back2未來; 03 December 2024, 02:09 AM.

      Comment

      Working...
      X