I have been holding off v2 with correct spacing before \ (seemingly
missed the first time) waiting for a review to confirm that this is
the right approach as agreed in IRC.
Let me know if anything else.
--
Jimmy
On Sat, Dec 19, 2015 at 10:57 PM, Jimmy Berry wrote:
> Removes the need to
Removes the need to set LIBVA_DRIVER_NAME=gallium for supported targets and is
consistent with vdpau and general gallium drivers.
Signed-off-by: Jimmy Berry
---
src/gallium/targets/va/Makefile.am | 14 ++
1 file changed, 14 insertions(+)
diff --git a/src/gallium/targets/va
For documentation purposes, we discussed things in IRC and should be
reflected in v6.
--
Jimmy
On Sat, Nov 7, 2015 at 10:49 PM, Ilia Mirkin wrote:
> On Sat, Nov 7, 2015 at 11:42 PM, Jimmy Berry wrote:
>> - env GALLIUM_HUD_VISIBLE: control default visibility
>> - env GALLIUM_HU
Do I need to do something to else to get this committed? Not 100% on process.
--
Jimmy
On Wed, Nov 4, 2015 at 2:32 AM, Samuel Pitoiset
wrote:
> Reviewed-by: Samuel Pitoiset
>
>
>
> On 11/04/2015 06:24 AM, Jimmy Berry wrote:
>>
>> ---
>> docs/envvars.h
On Mon, Nov 9, 2015 at 11:28 AM, Brian Paul wrote:
> On 11/07/2015 09:05 PM, Jimmy Berry wrote:
>>
>> - env GALLIUM_HUD_VISIBLE: control default visibility
>> - env GALLIUM_HUD_SIGNAL_TOGGLE: toggle visibility via signal
>> ---
>> docs/envvars.html
- env GALLIUM_HUD_VISIBLE: control default visibility
- env GALLIUM_HUD_SIGNAL_TOGGLE: toggle visibility via signal
---
Added fflush(stderr) per request.
docs/envvars.html | 6 ++
src/gallium/auxiliary/hud/hud_context.c | 29 +
2 files chang
- env GALLIUM_HUD_VISIBLE: control default visibility
- env GALLIUM_HUD_SIGNAL_TOGGLE: toggle visibility via signal
---
Added static to sig_handled as it should have been.
docs/envvars.html | 6 ++
src/gallium/auxiliary/hud/hud_context.c | 28 ++
- env GALLIUM_HUD_VISIBLE: control default visibility
- env GALLIUM_HUD_SIGNAL_TOGGLE: toggle visibility via signal
---
per imirkin's comments:
- long to unsigned
- ignore signal value of 0 rather than always printing error message (oversight)
docs/envvars.html | 6 ++
- env GALLIUM_HUD_VISIBLE: control default visibility
- env GALLIUM_HUD_SIGNAL_TOGGLE: toggle visibility via signal
---
docs/envvars.html | 6 ++
src/gallium/auxiliary/hud/hud_context.c | 28
2 files changed, 34 insertions(+)
diff --git a/do
Hi,
Changes are straightforward and make sense. I had a followup on one.
On Wed, Nov 4, 2015 at 10:14 AM, Mike Lothian wrote:
> Hi
>
> On Wed, 4 Nov 2015, 8:53 a.m. Samuel Pitoiset
> wrote:
>
> Hi Jimmy,
>
> Some comments below.
>
> On 11/04/2015 06:17 A
---
docs/envvars.html | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/envvars.html b/docs/envvars.html
index bdfe999..173c941 100644
--- a/docs/envvars.html
+++ b/docs/envvars.html
@@ -179,6 +179,8 @@ Mesa EGL supports different sets of environment variables.
See the
GALLIUM_HUD - dr
- env GALLIUM_HUD_VISIBLE: control default visibility
- env GALLIUM_HUD_SIGNAL_TOGGLE: toggle visibility via signal
---
Thanks for the feedback.
I believe all the suggested changes have been implemented.
One note, all the logic except for the toggle was already in hud_create() and
not hud_draw().
Some I managed to not end up with [PATCH] in subject or my coverletter.
This is my first patch to mesa-dev. Hopefully, I have done everything correctly.
I posed the idea about a week ago:
Manipulate GALLIUM_HUD post-launch (interactively)
http://lists.freedesktop.org/archives/mesa-dev/20
I have found myself desiring the ability to manipulate the GALLIUM_HUD
variable while an application is running. At the most basic simply
being able to toggle the hud on and off would be great. Otherwise, one
has to relaunch an application and get back to the same state which
may not always be triv
14 matches
Mail list logo
