Page 1 of 9 123 ... LastLast
Results 1 to 10 of 104

Thread: Luc Calls For A Dead Linux Desktop If Keith Gets His Way

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    15,110

    Default Luc Calls For A Dead Linux Desktop If Keith Gets His Way

    Phoronix: Luc Calls For A Dead Linux Desktop If Keith Gets His Way

    While X Server 1.10 is not being discussed at length until tomorrow (the final day of XDS Toulouse), besides today's notes, Luc Verhaegen who formerly was with Novell working on the RadeonHD driver and has also worked on the open-source VIA Unichrome driver and a few other X related projects, is preparing for another heated battle...

    http://www.phoronix.com/vr.php?view=ODYxMw

  2. #2
    Join Date
    Dec 2008
    Location
    Australia
    Posts
    880

    Default

    Merging the drivers back in doesn't exactly scream "best practice" to me.

  3. #3
    Join Date
    Jan 2010
    Location
    Somewhere in Kansas.
    Posts
    280

    Default

    Please don't demodulate it! It's bad enough that you have to upgrade the kernel for driver updates. Please don't make the graphic stack have the same issue.

  4. #4
    Join Date
    Nov 2009
    Location
    Italy
    Posts
    970

    Default

    Let's break the damn APIs, but please do not merge the video drivers back.

  5. #5
    Join Date
    Oct 2007
    Posts
    90

    Default

    De-modularizing the video drivers would be insane. Modular systems upgrade their APIs all the time, and it isn't painless but it is possible to do.

    If it is just the input drivers, then that is more understandable.

  6. #6
    Join Date
    Jun 2009
    Posts
    2,932

    Default

    The Nvidia driver is the WORST example of demodularisation.

    If we follow that direction, each driver would implement pretty much all of the X server and Gallium3d internally.

  7. #7
    Join Date
    May 2007
    Location
    Nurnberg.
    Posts
    327

    Default

    Quote Originally Posted by pingufunkybeat View Post
    The Nvidia driver is the WORST example of demodularisation.

    If we follow that direction, each driver would implement pretty much all of the X server and Gallium3d internally.
    This is not what is proposed here, this is not why the nvidia driver is mentioned.

    The nvidia driver was mentioned, because it is the most popular, and the one we hear the least people complain about. The reason for that is: it just works for more of the time than any of the other drivers out there.

    One major part of that is: people can just grab it and install it, and be pretty secure in that nothing else in their system, except the nvidia graphics driver stack itself, will change.

    This is what we can learn from nvidia (and unichrome, and to some lesser extent sis and radeonhd)

  8. #8
    Join Date
    Jun 2009
    Posts
    2,932

    Default

    Quote Originally Posted by libv View Post
    This is not what is proposed here, this is not why the nvidia driver is mentioned.

    The nvidia driver was mentioned, because it is the most popular, and the one we hear the least people complain about. The reason for that is: it just works for more of the time than any of the other drivers out there.

    One major part of that is: people can just grab it and install it, and be pretty secure in that nothing else in their system, except the nvidia graphics driver stack itself, will change.

    This is what we can learn from nvidia (and unichrome, and to some lesser extent sis and radeonhd)
    Thanks for your reply.

    But it still seems that it is exactly this duplication of effort (i.e. Nvidia designs everything, from the kernel parts to the high-level interfaces with only their hardware in mind and reduplicates much of the code in X, the kernel and Gallium3d) that leads to this.

  9. #9
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,798

    Default

    Quote Originally Posted by pingufunkybeat View Post
    Thanks for your reply.

    But it still seems that it is exactly this duplication of effort (i.e. Nvidia designs everything, from the kernel parts to the high-level interfaces with only their hardware in mind and reduplicates much of the code in X, the kernel and Gallium3d) that leads to this.
    The Catalyst driver doesn't do much of that stuff and compatibility is still there. So no, it's not "it" that leads to this.

  10. #10
    Join Date
    Jun 2009
    Posts
    2,932

    Default

    Quote Originally Posted by RealNC View Post
    The Catalyst driver doesn't do much of that stuff and compatibility is still there. So no, it's not "it" that leads to this.
    What do you mean?

    Catalyst does pretty much the same things the Nvidia blob does.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •