Originally posted by timofonic
View Post
Announcement
Collapse
No announcement yet.
ARB_enhanced_layouts Lands In Mesa Git, Rounds Out OpenGL 4.4 For RadeonSI
Collapse
X
-
Originally posted by atomsymbolOk. But I don't see how the document prevents OpenGL implementations from reporting version 4.4 to OpenGL applications.
Comment
-
Originally posted by atomsymbolIs it possible for Mesa to be a non-conformant OpenGL 4.4 implementation? In other words, are non-conformant OpenGL 4.4 implementations illegal?
Unofficialy you can do whatever you want as always, to the point of even inventing your own graphic API and of course name it as you wish.
Comment
-
Originally posted by atomsymbolI just want to know whether we can expect Mesa to report 4.4 to OpenGL applications without Mesa paying $25000 or $30000 to khronos.
Whatever, user alone can just override it if he wants, in similar way as building mesa with texture-float or using s3tc lib...
Comment
-
Originally posted by atomsymbol
I just want to know whether we can expect Mesa to report 4.4 to OpenGL applications without Mesa paying $25000 or $30000 to khronos.
From the PDF documents mentioned in this discussion it seems that Mesa will need to pay the fee if it wants glxinfo to output "OpenGL core profile version string: 4.4 (Core Profile) Mesa ...".Michael Larabel
https://www.michaellarabel.com/
- Likes 5
Comment
-
Originally posted by Michael View Post
I emailed the Khronos President who I communicate with regularly to try to get some clarification and if the open-source implementations would have any exemption... Did it this morning, waiting to hear back.
- Likes 1
Comment
-
Originally posted by Michael View Post
I emailed the Khronos President who I communicate with regularly to try to get some clarification and if the open-source implementations would have any exemption... Did it this morning, waiting to hear back.
Comment
-
Originally posted by geearf View Post
Intel and AMD can pay the fees easily, and most likely already do for Windows (and maybe phones too), I don't see why they would care:
That leaves the community drivers.
enable an Adopter to submit an unlimited number of products for that API (and any earlier versions as indicated in the table below).
AMD and Intel already payed those fees (for their hardware and for their windows drivers, AMD also for their amdgpu-pro driver).
Since they both work actively on the project, they can advertise it towards Kronos as one of their products and submit it for confirmation.
It's a bit different for Nouveau, since (to my knowledge), Nvidia doesn't take part here, at least not actively.
- Likes 1
Comment
-
Originally posted by Berniyh View Post
I don't see why there would be the need to pay the fee for the Intel and the r600/radeonsi driver.
AMD and Intel already payed those fees (for their hardware and for their windows drivers, AMD also for their amdgpu-pro driver).
Since they both work actively on the project, they can advertise it towards Kronos as one of their products and submit it for confirmation.
Comment
Comment