FWIW this works by emulation of these formats - mesa will uncompress them when specified to some uncompressed format. This means though there's zero benefit in using them over uncompressed formats (same memory requirements and performance when texturing, just increased overhead when specifying the texture). Though of course I guess this still saves disk space :-). Unlike etc1, which should work "natively" though as a result is currently very slow.
Roland Am 31.03.2015 um 21:07 schrieb Ilia Mirkin: > It should work fine, AFAIK. It's required by ES 3.0, and as you can > see, llvmpipe exposes ES 3.0 contexts: > > https://urldefense.proofpoint.com/v2/url?u=http-3A__people.freedesktop.org_-7Eimirkin_glxinfo_glxinfo.html-23p-3Des&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=Vjtt0vs_iqoI31UfJxBl7yv9I2FeiaeAYgMTLKRBc_I&m=iLPj6aKo64R-X4WRq15Niwc9-D6J6nBcxwNvnKzusyQ&s=hLUUCo2x4GrkbQhw-w0fJshn2dXmxUj1QfVV7PEcBos&e= > > > On Tue, Mar 31, 2015 at 3:03 PM, Shervin Sharifi <sherv...@gmail.com> wrote: >> Hi, >> >> I was wondering what's the status of ETC2 support with llvmpipe backend. >> _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev