Otherwise, displays driven by GPU screens remain on all the time.
Signed-off-by: Aaron Plattner aplatt...@nvidia.com
---
hw/xfree86/common/xf86DPMS.c | 45 ++--
1 file changed, 31 insertions(+), 14 deletions(-)
diff --git a/hw/xfree86/common/xf86DPMS.c
Peter Hutterer peter.hutte...@who-t.net writes:
Peter Hutterer (14):
test/signal-logging: simplify tests using sprintf
Reviewed-by: Keith Packard kei...@keithp.com
os: silently ignore length modifiers in pnprintf
Reviewed-by: Keith Packard kei...@keithp.com
os: add
The only drivers I can find that used this are the r128 and radeon DRI
drivers. r128 is dead and the radeon driver wasn't including Xorg's
compiler.h and still worked.
---
hw/xfree86/common/compiler.h | 15 ---
1 file changed, 15 deletions(-)
diff --git a/hw/xfree86/common/compiler.h
On Thu, Feb 7, 2013 at 5:29 PM, Matt Turner matts...@gmail.com wrote:
The only drivers I can find that used this are the r128 and radeon DRI
drivers. r128 is dead and the radeon driver wasn't including Xorg's
compiler.h and still worked.
---
Oh, and
Signed-off-by: Matt Turner
The transformation matrix we previously stored was a scaled matrix based on
the axis ranges of the device. For relative movements, the scaling is not
required (or desired).
Store two separate matrices, one as requested by the client, one as the
product of [scale . matrix . inv_scale]. Depending
On Thu, Feb 07, 2013 at 04:53:55PM -0800, Keith Packard wrote:
Peter Hutterer peter.hutte...@who-t.net writes:
Peter Hutterer (14):
test/signal-logging: simplify tests using sprintf
Reviewed-by: Keith Packard kei...@keithp.com
os: silently ignore length modifiers in
Keith, this is the list of fixes that should go into 1.14. Missing from this
is the relative transformation matrix, and it includes the ptraccel
debugging printf with your rev-by attached (which I just assumed)
Id' still like to get the relative matrix in as well, but that still needs
review.
Protocol (sort-of [1]) requires us to deliver motion events before button
events. For emulated events, the requirement is:
* TouchBegin: motion + button press
* TouchUpdate: motion
* TouchEnd: motion + button release
The TouchUpdate was handled through normal deliver, changing the TouchUpdate
Peter Hutterer peter.hutte...@who-t.net writes:
This is mostly sigsafe code, so use sigsave printf. And update some fields
to double that used to be int.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
Reviewed-by: Keith Packard kei...@keithp.com
--
keith.pack...@intel.com
Peter Hutterer peter.hutte...@who-t.net writes:
The transformation matrix we previously stored was a scaled matrix based on
the axis ranges of the device. For relative movements, the scaling is not
required (or desired).
Store two separate matrices, one as requested by the client, one as the
Peter Hutterer peter.hutte...@who-t.net writes:
fwiw, this isn't API, it's only used internally. did half of what you
suggested, rel matrix is stored without zero mangling now, but abs axis is
renamed, both for obviousness and the compiler telling me where I forgot the
update.
Better than my
Peter Hutterer peter.hutte...@who-t.net writes:
From what you said you don't need the client-requested version anyway, so
for now we don't actually need this new request after all.
That's the best kind of patch :-)
--
keith.pack...@intel.com
pgpUVWi3Olnbo.pgp
Description: PGP signature
Peter Hutterer peter.hutte...@who-t.net writes:
Keith, this is the list of fixes that should go into 1.14. Missing from this
is the relative transformation matrix, and it includes the ptraccel
debugging printf with your rev-by attached (which I just assumed)
Id' still like to get the
13 matches
Mail list logo
