[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] some samples and a question about looping
- To: Mark Callow <callow_mark@hicorp.co.jp>
- Subject: Re: [Public WebGL] some samples and a question about looping
- From: David Sheets <kosmo.zb@gmail.com>
- Date: Wed, 5 Jan 2011 21:23:21 -0800
- Cc: tomi.aarnio@nokia.com, public_webgl@khronos.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=u2P3yvCUQi4lCZApV7gavbw5qBtjpJhzQUHs8kqA+pQ=; b=FpoVpcoAmwwtaHASsoJ+PimC18Zd7IO0LmDC1jqLlOY+04/lxQ+BTAK7AzRxBHCXoE b/Vrksj6x+4fB8oQL3er7fxyan+qpMLZuftBAuNbB23P0eb2sB9QyCbMdluHtCOmNN5E F5y/fvrBuuEJ1GCEYTU77pbnIEocPQpi+zRgA=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qFMQ2kshuc9PQpFdjVoZyKJLt9xub4BlalI7sBSUpkR0mj/pmDShP8f3WkPbAUjEYN ftP3/R/IdO5OCp/V6GLLHVZc9wTkoWj+aWG7fkRdvH6Y9OexSoAVtNIymSNLPBU5uQnW igZHrgNz1DHZWGX3uwVuFXBsgjLBRsORUtotA=
- In-reply-to: <4D25294A.6010903@hicorp.co.jp>
- List-id: Public WebGL Mailing List <public_webgl.khronos.org>
- References: <AANLkTi=hd-eWqRT_PYLzwNXX0Hg_ebdVDONkP=jxiMd7@mail.gmail.com> <4D15F103.8020602@sjbaker.org> <AANLkTi=ZJqFYwHyCWSHU0aPv1DSc3gx5sojp2HZprTkh@mail.gmail.com> <4D180536.8090601@hicorp.co.jp> <AANLkTik17hHUMiwpw4rh+ZguDWpe2UJXeLAG=zfxz=yh@mail.gmail.com> <4D1A4D39.1010907@sjbaker.org> <AANLkTinjNXQh0k__6UkEp+QwwnAdfccGp2ssoynT-+xt@mail.gmail.com> <4D23D753.2050007@hicorp.co.jp> <9E85EB37BE49424480E1829239B6C9C511095E@008-AM1MPN1-015.mgdnok.nokia.com> <4D25294A.6010903@hicorp.co.jp>
- Sender: owner-public_webgl@khronos.org
Hi Mark,
I understand the desire to protect graphics vendors' interests by
making hardware limitation inquiries anonymous. Could you tell us
anything about the nature of these shader-limited GPUs? Are they
currently being manufactured? Are they 2 years old? 5 years? Desktop?
Phone?
If these GPUs are deployed in devices with sub-1GHz CPUs, I have a
hard time believing that these devices will ever run WebGL content
acceptably due to JavaScript's inherent inefficiency.
When WebGL starts to take off in a year or two, how old will these
minimally ES2 GPUs be? Will the owners of these devices expect WebGL
to work on a 5 year old cell phone?
I look forward to your reply.
Kindly,
David Sheets
Ashima Arts
On Wed, Jan 5, 2011 at 6:30 PM, Mark Callow <callow_mark@hicorp.co.jp> wrote:
> On 06/01/2011 01:02, tomi.aarnio@nokia.com wrote:
>> Hi Mark,
>>
>> Can you give any examples of such implementations? I'm wondering whether such hardware will be able to run any practical WebGL content in the first place, irrespective of looping restrictions.
> I think Ken's reply covered the situation pretty well. I can't give
> examples of such implementations because in the OpenGL ES WG we take
> steps to make responses to queries about hardware limitations anonymous.
> But when we discussed relaxing (strengthening?) the minima of Appendix A
> this feature was apparently not available on all implementations.
>
> Regards
>
> -Mark
>
-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email: