[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] OpenGL ES 2.0 driver for desktop
- To: Mark Callow <firstname.lastname@example.org>
- Subject: Re: [Public WebGL] OpenGL ES 2.0 driver for desktop
- From: "Gregg Tavares (wrk)" <email@example.com>
- Date: Sun, 8 Aug 2010 10:05:40 -0700
- Cc: public webgl <firstname.lastname@example.org>
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1281287146; bh=XIUWqdzwWqUfxIUskWWzTKXt12o=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=yuaYDt+zUtI65Z0J8xDLdnTYIS9iMKRN6LFbqOrnUT1RHtpqgpX5bx2sLUV4M81q+ ZHdzM/768XysZq1DvMNNA==
- Domainkey-signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=gSb00mjd2hRjDL+ANoih4I+aQ0tAmiIuNXfBhgthmiMGS1f+27tv1B8ZqyZ+EEVLy 2IcB/3L90hOHgJPgS/KWQ==
- In-reply-to: <4C5C4A0A.email@example.com>
- References: <4C5C4A0A.firstname.lastname@example.org>
- Sender: email@example.com
On Fri, Aug 6, 2010 at 10:44 AM, Mark Callow <firstname.lastname@example.org>
Of direct interest to WebGL implementers, and likely of interest to
others on this list, AMD last week at Siggraph announced
OpenGL ES 2.0 drivers for their desktop graphics cards.
Paradoxically it will probably complicate things for WebGL
implementations running on the desktop that wish to use this driver
when available. Hopefully other desktop graphics vendors will follow
suit, thus removing the complication.
BTW, these AMD drivers pass the OpenGL ES 2.0 conformance tests.
That's awesome that this is progressing. Unfortunately WebGL is far stricter than the OpenGL ES 2.0 conformance tests since we want WebGL to support only 2.0 with no extensions. That means the amount of work required to implement WebGL on top of OpenGL vs OpenGL ES 2.0 is really about the same. All enums have to be checked to reject extensions, NPOT textures have to be checked for and 2.0 restrictions enforced even in the presence of GL_OES_texture_npot, Buffers have to be checked out of range access on draw calls, shaders have to be checked they are not using any non 2.0 features, etc...