Page 4 of 4 FirstFirst ... 234
Results 31 to 36 of 36

Thread: R600 Gallium3D Getting Close On OpenGL 3.3 Support

  1. #31
    Join Date
    Jun 2010
    Posts
    763

    Default

    Quote Originally Posted by rrohbeck View Post
    /opt/xorg/share/X11/xorg.conf.d/50-Device: Driver "ati"
    It was my impression, that the ddx was called "radeonsi" or at least "radeon" and not "ati".

    Your Xorg.0.log says
    Code:
    [  1169.313] (II) LoadModule: "radeon"
    so your Device section with the "ati" driver is probably not used.


    Edit:
    Code:
    --with-dri-drivers=radeon
    Pretty sure, that doesn't do anything. But it may be necessary to put swrast there if it doesn't compile because of som stupid build system dependency. If not, Just a space character will be interpreted as an empty list, otherwise it will build some default like r300 I think.
    Last edited by ChrisXY; 01-21-2013 at 07:01 PM.

  2. #32
    Join Date
    Nov 2011
    Location
    Orange County, CA
    Posts
    47

    Default

    Quote Originally Posted by ChrisXY View Post
    It was my impression, that the ddx was called "radeonsi" or at least "radeon" and not "ati".

    Your Xorg.0.log says
    Code:
    [  1169.313] (II) LoadModule: "radeon"
    so your Device section with the "ati" driver is probably not used.


    Edit:
    Code:
    --with-dri-drivers=radeon
    Pretty sure, that doesn't do anything. But it may be necessary to put swrast there if it doesn't compile because of som stupid build system dependency. If not, Just a space character will be interpreted as an empty list, otherwise it will build some default like r300 I think.
    Changing the DDX name to "radeon" or "radeonsi" didn't make a difference. Neither did adding swrast to --with-dri-drivers.

  3. #33
    Join Date
    Nov 2011
    Location
    Orange County, CA
    Posts
    47

    Default

    Quote Originally Posted by agd5f View Post
    Is it actually getting picked up by the xserver however? Previously it was not. Can you post your xorg log? It would be easier to track all of this if you opened a bug:
    https://bugs.freedesktop.org
    Done, https://bugs.freedesktop.org/show_bug.cgi?id=59703

  4. #34
    Join Date
    Jan 2009
    Posts
    518

    Default

    Quote Originally Posted by ChrisXY View Post
    It was my impression, that the ddx was called "radeonsi" or at least "radeon" and not "ati".
    The DDX is really called "ati", which should load "radeon" for you.

    Quote Originally Posted by ChrisXY View Post
    Edit:
    Code:
    --with-dri-drivers=radeon
    Pretty sure, that doesn't do anything. But it may be necessary to put swrast there if it doesn't compile because of som stupid build system dependency. If not, Just a space character will be interpreted as an empty list, otherwise it will build some default like r300 I think.
    "--with-dri-drivers=radeon" builds the R100 driver. Just set empty "--with-dri-drivers=" and set "--with-gallium-drivers=" to one of r300, r600, radeonsi. I think you also need to enable EGL.
    Last edited by marek; 01-22-2013 at 02:06 PM.

  5. #35
    Join Date
    Jun 2010
    Posts
    763

    Default

    Quote Originally Posted by marek View Post
    The DDX is really called "ati", which should load "radeon" for you.
    Good to know. X -configure always generated "radeon" for me so I wrongly assumed it was radeon.

    Quote Originally Posted by marek View Post
    "--with-dri-drivers=radeon" builds the R100 driver. Just set empty "--with-dri-drivers=" and set "--with-gallium-drivers=" to one of r300, r600, radeonsi. I think you also need to enable EGL.
    I think I had two times a problem with mesa git with that. First for some reason the build system depended on swrast being built and much later it wouldn't compile without a dri driver. These problems get fixed but they seem to be recurring, so I guess there isn't too much ongoing testing going into specialized builds from git master…

  6. #36
    Join Date
    Nov 2011
    Location
    Orange County, CA
    Posts
    47

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
  •