Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Google's Chromium Running On Wayland

  1. #1
    Join Date
    Jan 2007
    Posts
    13,411

    Default Google's Chromium Running On Wayland

    Phoronix: Google's Chromium Running On Wayland

    The Chromium web-browser is back to running on Wayland...

    http://www.phoronix.com/vr.php?view=MTA5Njg

  2. #2
    Join Date
    Mar 2011
    Posts
    71

    Default

    Wayland minimum requirements are too high.My intel gma 950 does not have OpenGL ES 2.0

  3. #3
    Join Date
    Oct 2008
    Posts
    2,908

    Default

    Quote Originally Posted by lapis View Post
    Wayland minimum requirements are too high.My intel gma 950 does not have OpenGL ES 2.0
    We already have a system that runs on old hardware. It's called X.

  4. #4
    Join Date
    Oct 2009
    Posts
    341

    Default

    Quote Originally Posted by lapis View Post
    Wayland minimum requirements are too high.My intel gma 950 does not have OpenGL ES 2.0
    x86_64 minimum requirements are too high. my celeron 2.0ghz doesnt have amd64

  5. #5
    Join Date
    Mar 2011
    Posts
    71

    Default

    Quote Originally Posted by smitty3268 View Post
    We already have a system that runs on old hardware. It's called X.

    Not entirely true.It's the system which requires more resources to do the same thing.

  6. #6
    Join Date
    Oct 2009
    Posts
    353

    Default

    Quote Originally Posted by lapis View Post
    Wayland minimum requirements are too high.My intel gma 950 does not have OpenGL ES 2.0
    update your shit

  7. #7
    Join Date
    Oct 2008
    Posts
    2,908

    Default

    To be clear:

    The GL ES 2.0 requirement is simply a requirement that the hardware supports programmable shaders.

    That is a BIG fundamental requirement. Without that support, you may as well just stick to X, there is a ton of stuff that must be worked around, papered over, and emulated on the CPU.

    For simplicity sake, that hardware will be abandoned going forward. You should either stick with legacy code (X) or upgrade your hardware.

    Sorry, but hardware that crappy just isn't worth supporting with new code.

  8. #8
    Join Date
    Jun 2009
    Posts
    2,908

    Default

    LOL at calling X "legacy code".

    Just for a recap, when is Wayland expected to support accelerated OpenGL (not the ES kind, the full thing)?

  9. #9
    Join Date
    Oct 2008
    Posts
    2,908

    Default

    Quote Originally Posted by pingufunkybeat View Post
    LOL at calling X "legacy code".

    Just for a recap, when is Wayland expected to support accelerated OpenGL (not the ES kind, the full thing)?
    I don't think anyone is planning that right now, although it wouldn't be hard. I think ES2 is basically a subset of GL2, which throws out all the legacy/fixed function parts.

    The mesa drivers support ES2, and I think both NVidia and AMD do as well (or at least they have that ability for some of their drivers), so I'm not sure there will be any reason to support regular GL2, but if it becomes an issue I bet someone will fix it pretty quickly.

  10. #10
    Join Date
    Jun 2009
    Posts
    2,908

    Default

    Somebody correct me if I'm wrong, but I thought that the problem was that libGL from Mesa was heavily tied to X, and cleaning that is quite an undertaking.

    It just seems funny that people are complaining so vocally that OpenGL 4 apps don't run on Linux (there's 2 of them. TWO!), yet get excited about a system which does not support basically any existing native OpenGL software.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •