xserver/hw/modes: compat_output bad dereference.
The commit 37d956e3ac9513b74078882dff489f9b0a7a5a28 into
xserver/hw/modes/xf86Crtc.c xf86CrtcConfigInit() initializes
config->compat_output = -1;
So an unset compat_output is now invalid, a good property since the
previous initial compat_ou
The commit 37d956e3ac9513b74078882dff489f9b0a7a5a28 into
xserver/hw/modes/xf86Crtc.c xf86CrtcConfigInit() modified the
initialization of config->compat_output from default 0 to -1.
This change exposes a bug. During initial configuration a monitor
detection is attempted and if an EDID block is ava
The event struct is different, causing memory corruption on 1.13 and 1.14,
as can be witnessed in https://bugs.freedesktop.org/show_bug.cgi?id=56578
Signed-off-by: Maarten Lankhorst
---
Applies cleanly to 1.14, but will conflict with Peter Hutterer's proposed
patches.
It's trivial to fix, beca
Hello,
My name is Samprit Biswas and I am a sophomore student at the Indian
Institute of Technology Kharagpur, India of the department of Computer
Science and Engineering. I would like to join the X.org project as a
student on the Google Summer of Code program 2013.
I am particularly interested i
As some of you may know, the X.Org Foundation was accepted as a GSoC
Project for 2013. If you would be interested in participating as
either a mentor or a student, please sign up here:
http://www.google-melange.com/gsoc/homepage/google/gsoc2013
For students, you can see some potential projects id
On Mon, Apr 08, 2013 at 03:50:16PM -0700, Keith Packard wrote:
> Dave Airlie writes:
>
> > Don't think I did, from what I can see these are just local Ubuntu
> > races at startup between plymouth, lightdm and X,
>
> Maybe I was misreading stuff, but I saw a separate kernel thread about
> the X s
Write the swapped values to the destination rather than the source.
Signed-off-by: Keith Packard
---
Xi/extinit.c | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/Xi/extinit.c b/Xi/extinit.c
index 619d0e4..02fffe5 100644
--- a/Xi/extini
Whoops.
Reviewed-by: Jasper St. Pierre
On Tue, Apr 9, 2013 at 7:23 PM, Keith Packard wrote:
> Write the swapped values to the destination rather than the source.
>
> Signed-off-by: Keith Packard
> ---
> Xi/extinit.c | 36 ++--
> 1 file changed, 18 insertion
Bryce Harrington writes:
> So, feel free to revert the patches if the thinking is it's just adding
> clutter, but you may still want the first patch in the series as it adds
> a missing close(). We also found that having the server print out the
> error code helped in diagnosing the problem.
Th
Maarten mentioned that they were seeing problems with two X servers
running and hotplugging the USB output devices.
This set adds a cleaner interface for vt owner, it also
uses it to queue output devices.
Dave.
___
xorg-devel@lists.x.org: X.Org developm
This is just a simple interface to avoid accessing x86Screens[0]
directly.
Signed-off-by: Dave Airlie
---
hw/xfree86/common/xf86.h | 1 +
hw/xfree86/common/xf86Events.c | 9 +
2 files changed, 10 insertions(+)
diff --git a/hw/xfree86/common/xf86.h b/hw/xfree86/common/xf86.h
index
This replaces some previous uses of direct xf86Screens[0] accesses.
Signed-off-by: Dave Airlie
---
hw/xfree86/common/xf86Events.c | 2 +-
hw/xfree86/common/xf86Init.c | 2 +-
hw/xfree86/common/xf86Xinput.c | 2 +-
hw/xfree86/os-support/solaris/sun_init.c | 2 +-
4
We don't want to hotplug output devices while we are VT switched,
as we get races between multiple X servers on the device open, and
drm device master status. This just queues device opens until we return
from VT switch.
Signed-off-by: Dave Airlie
---
hw/xfree86/common/xf86Events.c |
13 matches
Mail list logo
