Contains fixes for following issues:
CVE-2015-1802: bdfReadProperties: property count needs range check
CVE-2015-1803: bdfReadCharacters: bailout if a char's bitmap cannot be read
CVE-2015-1804: bdfReadCharacters: ensure metrics fit into xCharInfo struct
does not always report a 0 'w' value for two-finger contacts.
Diff from Ulf Brosziewski.
Fix a regression with Synaptics touchpads reported by Patrick keshishian
and Henrik Friedrichsen on misc@.
ok matthieu@, deraadt@
those are the only archs that currently use gallium radeon drivers.
It should build anywhere that has the libdrm radeon headers
installed. And while that should really be everywhere it
isn't at the moment and won't be for release.
It isn't clear why the radeon winsys in Mesa 10.4 didn't have
the same problem.
Found the hard way by todd@ on alpha.
This is desirable as the chromium port now uses this extension to
obtain pci vendor/device ids for use in feature/extension blacklists.
Prompted by a mail from byrnet@, tested on r600g by krw@
The newly added os_get_total_physical_memory() was passing the length of
a pointer rather than the type which made the sysctl call fail on
non 64 bit archs. And it was passing the wrong pointer for the result.
Fixes for these problems have been submitted back upstream.
With 10.4.3 gpu compositing on chromium would result in a black window
on older Intel parts (ie x60s with 945gm) and at least some discrete
Radeon parts. These problems do not seem to occur on recent Intel
parts, though those have coherent memory and hardware contexts.
It isn't clear what changes in Mesa are involved in the problem
though it also occurs with the 10.3 branch.
This prevents filling /var/log/Xorg.0.log when a device gets disconnected.
XXX more work is needed to actually disable it (and make it possible to
automatically re-enable it when it becomes available again).
completely avoids the risk of getting killed by a signal because the backing
storage isn't there.
Use the __-prefixed name for now, as we might still change the name.
ok deraadt@, matthieu@
This improve "two-finger scrolling" on synaptics and will allow to
have proper "click-and-drag" support on elantech.
Note that this change is needed because wsmouse(4)/wscons(4) do not
support multitouch events for the moment and every protocol supported
by pms(4) do its own translation to fake such events.
From Ulf Brosziewski, ok shadchin@
