Announcement

Collapse
No announcement yet.

VirGL Now Capable Of OpenGL 4.1 With Latest Mesa

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • dragon321
    replied
    Originally posted by kiaas View Post

    I was thinking about Gallium9 for D3D at least, but I suppose that even wine doesn't want to pull in support for it in mainline means there's no chance of VirGL pulling in support for that either. :/
    Probably because it's limited for Gallium drivers. On desktop only AMD and Nouveau are using Gallium. Nvidia or Intel don't.

    Leave a comment:


  • pal666
    replied
    Originally posted by schmidtbag View Post
    My only point is (from what I can tell) there's not that much work to do to make VirGL caught up with Mesa, compared to other drivers.
    your point is wishful thinking

    Leave a comment:


  • kiaas
    replied
    Originally posted by dragon321 View Post

    Probably not because Windows uses DirectX for acceleration.

    If you want DX acceleration on VirGL then you need to bring some translation from DX to OpenGL/Vulkan (when this driver will get Vulkan support). As I know VirtualBox works the same way - implements DX on OGL thats why you can use DX acceleration on Linux host.
    I was thinking about Gallium9 for D3D at least, but I suppose that even wine doesn't want to pull in support for it in mainline means there's no chance of VirGL pulling in support for that either. :/

    Leave a comment:


  • dragon321
    replied
    Originally posted by jacob View Post

    Is that enough for an accelerated desktop / MS office? I'm not talking games...
    Probably not because Windows uses DirectX for acceleration.

    If you want DX acceleration on VirGL then you need to bring some translation from DX to OpenGL/Vulkan (when this driver will get Vulkan support). As I know VirtualBox works the same way - implements DX on OGL thats why you can use DX acceleration on Linux host.
    Last edited by dragon321; 12 June 2018, 11:49 AM.

    Leave a comment:


  • schmidtbag
    replied
    Originally posted by pal666 View Post
    no hardware driver does any of the rendering. they command hardware to do rendering.
    *sigh* You really need to stop taking things so literally, especially where the specifics/accuracy doesn't invalidate the point. Yes, obviously the driver itself doesn't handle the rendering. I'm making a tremendously generalized summary with intentionally vague terminology, to make a quick point. What you said here...
    virgl is gallium driver. it does not talk to gallium hardware driver at the host because host does not have to have gallium hardware driver. virgl talks to opengl host driver, i.e. it has to convert gallium back to opengl
    ...is pretty much just a more accurate way of saying what I meant to say, with more specifics pertaining to Gallium. At least 1 other person seemed to understand the gist of what I meant.

    My only point is (from what I can tell) there's not that much work to do to make VirGL caught up with Mesa, compared to other drivers.

    Leave a comment:


  • pal666
    replied
    Originally posted by schmidtbag View Post
    It was implied I meant this summer (specifically, for the northern hemisphere), which I think is a reasonable estimate. Progress for VirGL is very fast, because (I assume) it doesn't actually do any of the rendering.
    no hardware driver does any of the rendering. they command hardware to do rendering.
    Originally posted by schmidtbag View Post
    I'm guessing the extensions are just simply redirected (maybe over a virtual network?) to the actual hardware drivers, so it really just comes down to testing if these redirections actually work.
    virgl is gallium driver. it does not talk to gallium hardware driver at the host because host does not have to have gallium hardware driver. virgl talks to opengl host driver, i.e. it has to convert gallium back to opengl
    Originally posted by schmidtbag View Post
    I'm guessing there's some behind-the-scenes work done, or else I think this would already have complete feature parity with current Mesa.
    your guess would be better with s/some/a lot of/
    virgl gallium driver is 3 times smaller than softpipe. but this is only one side of driver

    Leave a comment:


  • darkbasic
    replied
    Originally posted by Tomin View Post
    I wonder if you could run Wine's Direct3D over OpenGL on virtualized Windows to get some level of Direct3D support with VirGL.
    It makes no sense because we can use DX over Vulkan instead.

    Leave a comment:


  • ssorgatem
    replied
    Originally posted by Tomin View Post
    I wonder if you could run Wine's Direct3D over OpenGL on virtualized Windows to get some level of Direct3D support with VirGL.
    This is exactly what VirtualBox does.

    It is indeed possible; just replacing the native direct3d dlls with a native build of wine's wined3d.
    It's the same as using DXVK on Windows.

    Leave a comment:


  • Tomin
    replied
    Originally posted by starshipeleven View Post
    the level of abstraction is hurting me, please stop.
    Haha.

    Leave a comment:


  • starshipeleven
    replied
    Originally posted by Tomin View Post
    I wonder if you could run Wine's Direct3D over OpenGL on virtualized Windows to get some level of Direct3D support with VirGL.
    the level of abstraction is hurting me, please stop.

    Leave a comment:

Working...
X