tag:blogger.com,1999:blog-977684764667858073.post3773711208663713905..comments2024-02-09T21:43:15.143+00:00Comments on /bɑs ˈtjɛ̃ no ˈse ʁɑ/ (hadess) | News: Dual-GPU integration in GNOMEBastien Nocerahttp://www.blogger.com/profile/14621847888418739807noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-977684764667858073.post-60517412562063657142017-05-23T09:06:46.668+01:002017-05-23T09:06:46.668+01:00Dual GPU is not working under OpenSuse Tumbleweed....Dual GPU is not working under OpenSuse Tumbleweed...Anonymoushttps://www.blogger.com/profile/14081270681980053407noreply@blogger.comtag:blogger.com,1999:blog-977684764667858073.post-46650204506958036292017-02-16T03:35:54.611+00:002017-02-16T03:35:54.611+00:00@DimStar: I didn't even know something else ex...@DimStar: I didn't even know something else existed. I have no plans to do any further work on this, and certainly not attempt to run this under fd.o, the past attempts have just been too painful.Bastien Nocerahttps://www.blogger.com/profile/14621847888418739807noreply@blogger.comtag:blogger.com,1999:blog-977684764667858073.post-17934246147209949352017-02-16T00:07:27.919+00:002017-02-16T00:07:27.919+00:00KDE also implemented a simple dbus service that on...KDE also implemented a simple dbus service that only provides hasDualGPU - are there any plans to unite the two services instead of maintaining two?<br /><br />Might be worthy to move it under the org.freedesktop scope?DimStarhttps://www.blogger.com/profile/02698784722022202322noreply@blogger.comtag:blogger.com,1999:blog-977684764667858073.post-31860101020868159782016-10-27T12:07:44.928+01:002016-10-27T12:07:44.928+01:00@fschwarz: Using "core context" is kind ...@fschwarz: Using "core context" is kind of pointless because, for instance, GTK+ will always require a core profile context by default. If you have an intel IGP and an nvidia discrete card you'd likely get the exact same title.<br /><br />@Bastien: Could be useful to use GL_VENDOR instead of GL_RENDERER. But, yes: GL_RENDERER in Mesa is kind of busted for all Gallium-based renderers, and Mesa is the place to fix it appropriately.Emmanuelehttps://www.blogger.com/profile/14797939115552193382noreply@blogger.comtag:blogger.com,1999:blog-977684764667858073.post-19571405424453507532016-10-26T22:51:16.711+01:002016-10-26T22:51:16.711+01:00Those are from glGetString (GL_RENDERER). Fix thos...Those are from glGetString (GL_RENDERER). Fix those, and you've fixed the display in the Settings panel. In short, nothing that I can, or would want to, fix from my end.Bastien Nocerahttps://www.blogger.com/profile/14621847888418739807noreply@blogger.comtag:blogger.com,1999:blog-977684764667858073.post-18220479704129553492016-10-26T20:34:47.428+01:002016-10-26T20:34:47.428+01:00How about not showing "Gallium 0.4"? The...How about not showing "Gallium 0.4"? The gallium version number is rarely meaningful. Better to show the OpenGL (core context) version (which is interesting for AMD as you might have a really new mesa but don't get the highest OpenGL due to "outdated" LLVM).Anonymousnoreply@blogger.com