Announcement

Collapse
No announcement yet.

LLVMpipe Doesn't Yet Like The GNOME Shell

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

  • michael-vb
    replied
    Originally posted by airlied View Post
    Its kind of hard to do TFP in a direct rendered context with a sw renderer, since we rely on the drm to share the buffer objects between server/compositor.

    It needs llvmpipe in indirect context + some fixes in the server to do TFP in there.
    Unless the software renderer can get a handle on the X connection (which does make some sense for GLX stuff anyway). VirtualBox does this.

    Leave a comment:


  • cb88
    replied
    And whys should we believe just some-guy that happens to post to the phoronix forums :-P

    he is right though XD

    Leave a comment:


  • some-guy
    replied
    Originally posted by nanonyme View Post
    Though if we believe SmSpillaz - and why should we - it's more non-existing than broken.
    That's funny.

    SmSpillaz is the most active developer working on compiz, I think he know's what he's talking about.

    Next time try using google.

    Leave a comment:


  • airlied
    replied
    Originally posted by cb88 View Post
    @nanonyme yep I agree you can hardly call out developers for bugs in features that don't exist yet :-)

    @arlied does TFP have applications other than compiz? Textured video? seems that would be faster native anyway though.
    No its pretty much designed to be used for GL compositors, not sure anyone has found any other use for it.

    Dave.

    Leave a comment:


  • xir_
    replied
    Originally posted by cb88 View Post
    No you should offer a *good* experience to all users... loading down your CPU with bling will not do that. This is little more than proof of concept unless we get oct-channel ram and 16 way processing :-)

    If a computer doesn't have a 3d accelerator you shouldn't be doing 3d...and running compiz or gnomeshell would defeat the purpose of LLVMpipe as well (which is to make software rendering better as they would slow any 3d operations down in user software significantly.)

    LLVMpipe will let people without a 3d card and a fast CPU play a few opengl games... but little more

    I don't I necessarily agree. Whilst yes it is important not to bog down the cpu. It seems that gnome will be relying on graphic acceleration capable hardware more and more.


    The result from this is going to be a very modern (i.e blingy) desktop, I think that regardless though you will want to keep as many people as close to a homogeneous system as possible. Especially if you are selling support and telling people where graphic settings are hidden like canonical is.


    For people who don't even have a smidge of acceleration i think that there are more light weight distros to offer such as lubuntu or at a pinch xbuntu or my personal favorite #!.

    Leave a comment:


  • cb88
    replied
    @nanonyme yep I agree you can hardly call out developers for bugs in features that don't exist yet :-)

    @arlied does TFP have applications other than compiz? Textured video? seems that would be faster native anyway though.

    Leave a comment:


  • airlied
    replied
    Its kind of hard to do TFP in a direct rendered context with a sw renderer, since we rely on the drm to share the buffer objects between server/compositor.

    It needs llvmpipe in indirect context + some fixes in the server to do TFP in there.

    Leave a comment:


  • nanonyme
    replied
    Originally posted by drago01 View Post
    Well this looks like the glx_tfp implementation is broken (which also explains the white screen when running compiz).
    Though if we believe SmSpillaz - and why should we - it's more non-existing than broken.

    Leave a comment:


  • drago01
    replied
    Well this looks like the glx_tfp implementation is broken (which also explains the white screen when running compiz).

    Leave a comment:


  • hax0r
    replied
    Originally posted by tulcod View Post
    However, what you just posted is a blast. It's a bug report, and a particularly long one, too. You didn't provide a backtrace, not a hint where the problem may lie. You simply stated "hey, we tried running development software x on development software y, and it didn't work". And it only took you 608 words. Thank you for filling my feed reader, this is the best day of my life.
    Who said that he has to fill out bugs and give backtracks etc. It's reality. Go and fill out bugs yourself, like it's going to be fixed right away since no one knows about or cares.

    Leave a comment:

Working...
X