| Age | Commit message (Collapse) | Author |
|---|
|
- also rename via -> openchrome.
|
|
- add a reference to wsfb(4).
|
|
|
|
XAA PixmapOps: Sync before accessing unwrapped callbacks.
When using any XAAPixmapOps, we call into unknown but freshly
unwrapped callbacks (like fb ones). Unlike the XAA*Fallback calls,
we did so without syncing first, exposing us to all kinds of
synchronisation issues.
I believe that the rendering errors appeared now because *PaintWindow
vanished (e4d11e58), and we just use miPaintWindow instead. This
takes a less direct route to the hw and ends up at
PolyFillRectPixmap, which very often left drawing artifacts.
We now sync accordingly, and no longer get the rendering artifacts i
was methodically reproducing on radeonhd, radeon, unichrome...
Also, in order to allow driver authors to remove extensive syncing
or flushing to hide this issue, create XAA_VERSION_ defines, put
them in xaa.h and bump the patchlevel.
tested by naddy@ and Edd Barrett. ok oga@.
|
|
|
|
|
|
arch)
|
|
|
|
|
|
Gets rid of dangling /tmp/.X11-unix/X0 sockets after server crash.
|
|
disabled it on a few platforms.
|
|
|
|
|
|
on Ultra 5/10 machines.
ok matthieu@, oga@
|
|
Thanks.
|
|
(The IBM SurePos 500 has six serial lines and the touch screen is at
this device).
ok oga@
|
|
fiddle with it here. Pointed out by miod@.
ok matthieu@
|
|
|
|
ok matthieu@
|
|
sunffb driver.
ok matthieu@
|
|
PCI address space is completely seperate, so we don't have to claim any
resources to avoid clashes with main memory and firmware. Makes accelerated
graphics work on the Tadpole SPARCLE.
ok matthieu@, oga@
|
|
|
|
|
|
(This patch was missing form the bunch of security patches committed
on june 11. noticed by brad@).
|
|
|
|
|
|
ok matthieu
|
|
irritating.
|
|
privsep ( O_NONBLOCK | O_RDWR | O_EXCL) by turning the list of allowed
devices into a struct, with the flags we're supposed to use, then using
these values with open(). Add /dev/dri/card0 there too (more'll be needed to be
added when it matters).
This gives privsep with dri a chance to work.
ok matthieu
|
|
Reported to iDefense by regenrecht. Patch from Dave Airlie.
|
|
CVE-2008-2360 - RENDER Extension heap buffer overflow
CVE-2008-2361 - RENDER Extension crash
CVE-2008-2362 - RENDER Extension memory corruption
CVE-2008-1379 - MIT-SHM arbitrary memory read
CVE-2008-1377 - RECORD and Security extensions memory corruption
|
|
CPUs in basic VESA mode:
X86EMU: handle CPUID instruction
Starting X on an AMD Geode LX system such as an Alix board with VGA
connector, the Xorg driver attempts to issue INT 10/0 to go to mode
3 (VGA). The emulator, running the BIOS code, would then spit out:
c000:0282: A2 ILLEGAL EXTENDED X86 OPCODE!
The opcode was 0F A2, or CPUID; it was not implemented in the
emulator. With this patch it handles the CPUID instruction in one of
two ways:
1) if ran on __i386__ or __x86_64__ then it calls the CPUID instruction
directly.
2) if ran elsewhere it returns a canned 486dx4 set of values for function 1.
Tested with & ok matthieu
|
|
first place, and didn't work anyways.
ok deraadt, oga, matthieu
|
|
|
|
ioport and its symlinks and use that option. Requested by kettenis@
and others.
|
|
overwritten with the enqueueInputProc (from upstream git)
cf. https://bugs.freedesktop.org/show_bug.cgi?id=13511
This should fix hangs people were seeing with icewm, cwm and most
probably other WM under some circumstances.
ok matthieu@
|
|
|
|
at several places in the Xenocara build in a central place instead
of duplicating the checks all over the place. ok oga@.
|
|
each cmsg_len (ie. msg_controllen = sum of CMSG_ALIGN(cmsg_len). This
works now that kernel fd passing has been fixed to accept a bit of
sloppiness because of this ABI repair.
lots of discussion with kettenis. From deraadt@
|
|
|
|
CMSG_SIZE(sizeof(int)), not sizeof(buffer) which may be larger because
of alignment. Based on fixes in base system.
|
|
ok deraadt@
|
|
xkb: don't update LEDs if they don't exist (which would trigger an NULL
pointer dereference).
|
|
|
|
Don't break grab and focus state for a window when redirecting it.
Composite uses an unmap/map cycle to trigger backing pixmap allocation
and cliprect recomputation when a window is redirected or unredirected.
To avoid protocol visible side effects, map and unmap events are
disabled temporarily. However, when a window is unmapped it is also
removed from grabs and loses focus, but these state changes are not
disabled.
This change supresses the unmap side effects during the composite
unmap/map cycle and fixes a bug where a compositing window manager
would cause the screensaver to lose its grab when it unredirects the
fullscreen lock window.
|
|
|
|
|
|
|
|
|
|
|
