The hardware accelerated graphics API that the rest of the world has depended upon is OpenGL, minus Direct3D for obvious reasons. It's unfortunate, but if OpenGL isn't supported on these devices, a hardware accelerated desktop isn't going to be possible. I don't think it's worth it to write hardware acceleration code because the driver maintainers couldn't give us the API that everybody else has.
The issue should be fixed at the driver level, not at the GNOME level. On Thu, Nov 22, 2012 at 5:30 AM, Alan Cox <[email protected]> wrote: > It's a series of chipsets involved > > GMA500 ('Poulsbo') > GMA600 ('Oaktrail') > GMA3600 ('Cedartrail') > GMA3650 ('Cedartrail') > E6xx ('Tunnel Creek') > > The unaccelerated driver is quite happy with 2D desktops but LLVMpipe and > the paths used by the Gnome bling and compositing seem to hit it a lot > harder. > > That probably points to it being at least partly solvable by de-blinging > the Gnome3 desktop or optimising/changing how it renders. E for example > has multiple rendering back ends. > > Alan > _______________________________________________ > desktop-devel-list mailing list > [email protected] > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > -- Jasper
_______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
