Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: X Server 1.11 Breaks The Video Driver ABI

  1. #1
    Join Date
    Jan 2007
    Posts
    14,538

    Default X Server 1.11 Breaks The Video Driver ABI

    Phoronix: X Server 1.11 Breaks The Video Driver ABI

    While not exactly uncommon for a major X.Org Server update, the video driver ABI for the DDX drivers will break with the forthcoming xorg-server 1.11 release. This means that for those using the proprietary graphics drivers, namely the AMD Catalyst driver, you may be stuck waiting a couple of months for support...

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

  2. #2
    Join Date
    Oct 2007
    Posts
    1,267

    Default

    I didn't see a quick link to what improvements are in xserver 1.11 and whether I'll actually care if I can't use it.

  3. #3
    Join Date
    Nov 2008
    Posts
    12

    Default

    Oh man, breaking the ABI over some wasted bytes? Is that really worth it?

  4. #4
    Join Date
    Dec 2008
    Location
    Poland
    Posts
    118

    Default

    Quote Originally Posted by maleadt View Post
    Oh man, breaking the ABI over some wasted bytes? Is that really worth it?
    I think it's not worth it. In fact it is really stupid to give away so much and benefiting so little from this change.

  5. #5
    Join Date
    Nov 2008
    Posts
    56

    Default

    "...for those using the proprietary graphics drivers... you may be stuck waiting a couple of months for support."

    Yeah, because all the X development happens behind closed doors, so there's no opportunity to build for the changes until the last second. Oh no, wait, that's a lie. The proprietary driver developers can pick up the code at any time and add a few tests, so that the same blob works on either release. If their code isn't working on day one, it's not the Xorg developer's fault, it's the fault of Nvidia and AMD.

  6. #6
    Join Date
    Feb 2008
    Location
    California
    Posts
    79

    Default

    Quote Originally Posted by maleadt View Post
    Oh man, breaking the ABI over some wasted bytes? Is that really worth it?
    Note that's the first commit that changes ABI from xserver-1.10, but it's not the only one, and reverting just it would still leave the ABI incompatible.

  7. #7
    Join Date
    Jan 2008
    Posts
    772

    Default

    The next Xorg server version breaks the driver ABI, requiring users to wait for updates to proprietary drivers before upgrading the server.

    In other news, the Earth rotated today, creating a wave of darkness that required most of the planet's population to cease major work and travel activities for some 8 to 12 hours.

  8. #8
    Join Date
    Apr 2010
    Posts
    26

    Default

    Quote Originally Posted by macemoneta View Post
    "...for those using the proprietary graphics drivers... you may be stuck waiting a couple of months for support."

    Yeah, because all the X development happens behind closed doors, so there's no opportunity to build for the changes until the last second. Oh no, wait, that's a lie. The proprietary driver developers can pick up the code at any time and add a few tests, so that the same blob works on either release. If their code isn't working on day one, it's not the Xorg developer's fault, it's the fault of Nvidia and AMD.
    Who said it's the fault of Xorg devs?


    I think the Catalyst devs have better things to do than making their drivers work with the latest Xorg 1.11 code, such as making it work properly with the current Xorg.

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

    Default

    Quote Originally Posted by phoronix View Post
    In fact, it's usually not until the next Ubuntu Linux release with the new xorg-server that AMD puts out a supportive driver of that kernel / xorg-server.
    Since Microsoft has forbidden AMD to release Linux drivers sooner than Windows ones, that's to be expected. If AMD had some balls, this wouldn't be happening.

  10. #10
    Join Date
    Aug 2009
    Posts
    2,264

    Default

    Just update the freaking driver code and recompile, AMD and nVidia....

    Wayland is compatible with nothing at this time and if X.org can't even change such a minor problem than you can bet your X.org ass that Canonical is going to ship Wayland a lot sooner (they said they'd ditch the proprietary drivers whenever FLOSS becomes useful enough for them).

    And you know what time it is when Ubuntu starts changing...

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
  •