Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 40

Thread: "We have no plans to support Wayland."

  1. #11
    Join Date
    May 2007
    Location
    Third Rock from the Sun
    Posts
    6,532

    Default

    Quote Originally Posted by d2kx View Post
    Source: http://www.nvnews.net/vbulletin/show...2&postcount=11

    This is gonna be fun. But as long as they are happy launching the GTX 580 on tuesday that sucks more power than my whole computer...
    Means nothing at all. On pretty much any specific item about the linux drivers nvidia has always said "No plans at this time" until they are ready to release a driver to do so.

  2. #12
    Join Date
    May 2007
    Location
    Nurnberg.
    Posts
    302

    Default

    Quote Originally Posted by cl333r View Post
    At least Nvidia said it doesn't mind people creating open source drivers for their hardware (which is very good if you think about it), unlike for instance Microsoft, who recently vehemently opposed the intent of a third party to create open source drivers for their newly launched "Kinect".
    As I understand it, Nvidia doesn't offer open-source drivers because they're afraid they might be infringing some patents which would show up in the source code.. (I heard many companies do this for same reason, don't we all love software-patents?) but then I don't know why they won't even release documentation since AMD doesn't have (serious) problems neither with the source code nor with releasing documentation about its hw.
    When have you last seen documentation from ATI?

  3. #13
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,729

    Default

    Five months ago according to

    http://www.x.org/docs/AMD/

  4. #14
    Join Date
    May 2007
    Location
    Nurnberg.
    Posts
    302

    Default

    Quote Originally Posted by curaga View Post
    Five months ago according to

    http://www.x.org/docs/AMD/
    Which would be R5xx_Acceleration_v1.5.pdf ...

    I think only the firegl versions of those are still being actively sold.

  5. #15
    Join Date
    Dec 2007
    Posts
    2,276

    Default

    Just as the r5xx accel documentation applies to r3xx/r4xx for the most part, the r6xx/r7xx acceleration documentation still applies to evergreen as the 3D state registers did not change significantly as you can see:
    http://cgit.freedesktop.org/xorg/dri...een_reg_auto.h
    http://cgit.freedesktop.org/xorg/dri...eg_auto_r6xx.h
    What did change were the shaders, which are well documented here:
    http://developer.amd.com/documentati...s/default.aspx

  6. #16
    Join Date
    May 2007
    Location
    Nurnberg.
    Posts
    302

    Default

    Quote Originally Posted by agd5f View Post
    Just as the r5xx accel documentation applies to r3xx/r4xx for the most part, the r6xx/r7xx acceleration documentation still applies to evergreen as the 3D state registers did not change significantly as you can see:
    http://cgit.freedesktop.org/xorg/dri...een_reg_auto.h
    http://cgit.freedesktop.org/xorg/dri...eg_auto_r6xx.h
    What did change were the shaders, which are well documented here:
    http://developer.amd.com/documentati...s/default.aspx
    So what about register specs for the display, or maybe even the documentation for atombios?

  7. #17
    Join Date
    Dec 2007
    Posts
    2,276

    Default

    Unfortunately, we haven't had time to review and release register specs for the DCE4 display blocks yet. DCE1 (r5xx) and DCE2 (early r6xx/rs690/rs740) are available here:
    http://developer.amd.com/documentati...s/default.aspx
    and here:
    http://www.x.org/docs/AMD/
    and most of DCE3 (later r6xx/rs780/rs880, r7xx) is in the rs780 docs here:
    http://developer.amd.com/documentati...s/default.aspx

    At this point atombios is fairly well documented by the various parsers and utilities that have been released.

  8. #18
    Join Date
    Feb 2007
    Posts
    87

    Default

    Quote Originally Posted by deanjo View Post
    Means nothing at all. On pretty much any specific item about the linux drivers nvidia has always said "No plans at this time" until they are ready to release a driver to do so.
    Yes, just like with KMS, right? right? ....

  9. #19
    Join Date
    May 2007
    Location
    Third Rock from the Sun
    Posts
    6,532

    Default

    Quote Originally Posted by ioannis View Post
    Yes, just like with KMS, right? right? ....
    Search the nvnews.net linux forum for "purevideo support" and "sli support". You will see that nvidia didn't announce anything until they had a working solution.

  10. #20
    Join Date
    Oct 2007
    Posts
    19

    Default

    The nvidia driver already does KMS (mode setting in the kernel). What it doesn't have is a framebuffer console driver, so it can't do the seamless switching thing that everyone seems to think 'KMS' means. Also, as I understood it, doesn't wayland rely on EGL rather than KMS/GEM specifically? Shouldn't nvidia supporting GL outside of X be enough?

    Essentially, my point is that if we're going to ask the developers at nvidia to support things, we ought to ask for the actual things we want (EGL/fbdev etc) not implementation details from the open source drivers (KMS/GEM/TTM/DRI/mesa/gallium etc) which they will reject immediately, for obvious reasons.

    See: http://www.nvnews.net/vbulletin/showthread.php?t=129253 especially post 5

Posting Permissions

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