From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Trevor Woerner <twoerner@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] mesa: potentially enable texture float for gallium
Date: Tue, 30 May 2017 00:25:37 +0100 [thread overview]
Message-ID: <1496100337.25229.147.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170526212248.16374-1-twoerner@gmail.com>
On Fri, 2017-05-26 at 17:22 -0400, Trevor Woerner wrote:
> Somewhere along the path from OpenGL ES 2.0 to OpenGL ES 3.0 are some
> algorithms that are encumbered by patents. These algorithms are
> enabled with
> mesa's --enable-texture-float configure flag. However, if hardware
> acceleration is being used and the hardware supports --enable-
> texture-float,
> it means the hardware vendor has paid for the patents.
>
> This patch will add --enable-texture-float for any hardware-backed
> gallium
> mesa driver. In other words, if you are only using the software
> backup
> (swrast) you'll need to enable this flag if you know what you're
> doing (which
> assumes you are complying with the patent). Otherwise we enable this
> flag so
> the software can take full advantage of the hardware.
Does this handle the case where the driver may or may not run on a
platform with the relevant hardware? Some platforms add swrast as well
as hardware acceleration which based on what I read above, may breach
patents depending on which hardware its run on?
Cheers,
Richard
next prev parent reply other threads:[~2017-05-29 23:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 21:22 [PATCH] mesa: potentially enable texture float for gallium Trevor Woerner
2017-05-29 23:25 ` Richard Purdie [this message]
2017-05-30 5:28 ` Trevor Woerner
2017-05-30 7:47 ` Richard Purdie
2017-05-30 15:27 ` Trevor Woerner
2017-05-30 15:44 ` Richard Purdie
2017-05-30 16:00 ` Trevor Woerner
2017-05-30 16:19 ` Richard Purdie
2017-05-31 7:15 ` Jussi Kukkonen
2017-05-31 16:03 ` Trevor Woerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1496100337.25229.147.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=twoerner@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.