Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

Thread: OpenGL 3.0 Now Handled For All Of R600 Gallium3D

  1. #11
    Join Date
    Jun 2009
    Posts
    1,118

    Default

    hi marek, i did a git pull today since some patches naming r700 landed but it seem MSAA is not activated yet, i think is cuz i miss a patch that has not landed on git yet but just in case

    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD RV770
    OpenGL version string: 2.1 Mesa 8.1-devel (git-f8a8f06)
    OpenGL shading language version string: 1.30
    OpenGL extensions:

    03:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI R700 [Radeon HD 4850] (prog-if 00 [VGA controller])
    04:00.0 Display controller: Advanced Micro Devices [AMD] nee ATI R700 [Radeon HD 4850]
    4850X2 2GB
    xorg 1.13
    libdrm git
    3.6-rc2 kernel

  2. #12
    Join Date
    Nov 2009
    Posts
    379

    Default

    Btw. compared to Intel graphics... I can play DDO (wine), open driver on 1 cylinder (low power profile ~299MHz), all settings to high.

  3. #13
    Join Date
    Mar 2011
    Posts
    375

    Default

    Quote Originally Posted by jrch2k8 View Post
    3.6-rc2 kernel
    AFAIK the kernel bits are missing in rc2 (and rc3, too). Hopefully they will be in rc4.

  4. #14
    Join Date
    Jun 2009
    Posts
    1,118

    Default

    Quote Originally Posted by TAXI View Post
    AFAIK the kernel bits are missing in rc2 (and rc3, too). Hopefully they will be in rc4.
    thank you for your answer i boo boo and forgot to check kernel mailing list for patches

    ill try rc4 then thx

  5. #15
    Join Date
    Jul 2011
    Posts
    44

    Wink

    Quote Originally Posted by Dukenukemx View Post
    Give him a donate button and you'll be surprised how many people will donate.
    He has PayPal link in his profile (http://phoronix.com/forums/member.php?18270-marek) -- maraeo@gmail.com.

  6. #16
    Join Date
    Mar 2008
    Location
    Istanbul
    Posts
    134

    Thumbs up

    Quote Originally Posted by dogsleg View Post
    Hey dogsleg,
    Thanks for pointing his paypal account.
    I just send some financial aid for beer with help of you

  7. #17
    Join Date
    Oct 2010
    Posts
    309

    Default

    Quote Originally Posted by bridgman View Post
    Yeah, we discussed various naming options, but the bottom line was that when a new driver component is started we know the name of the first generation it will support but rarely know the name of the last generation... so r600g (src/gallium/drivers/r600 IIRC) covers r6xx through NI and radeonsi covers SI through <who knows ?>...
    Wouldn't radeongcn have been a better name then radeonsi?

  8. #18
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,405

    Default

    Quote Originally Posted by Ansla View Post
    Wouldn't radeongcn have been a better name then radeonsi?
    The problem is that we don't know what comes after GCN and whether it will also fit into the same driver. We kinda had two choices :

    - stay with the current naming convention based on "first supported generation"
    - rename existing drivers as well and go with architecture-based names

    Agree that the transitional product naming (where high end SI parts are GCN and lower parts are VLIW) makes the current naming convention awkward for now.

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
  •