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@
information based on GLX_MESA_query_renderer.
The glxinfo man page isn't present in mesa demos so switch our page to
mdoc and update the flags.
Prompted by an initial diff from brynet@
ok brynet@ kettenis@
Tested by matthieu@ mpi@ and myself. landry@ ran a ports bulk build.
kettenis@ tracked down the cause of an alignment fault on archs
that require strict eight byte pointer alignment.
from re-hiding on restart due to flag toggling (note that this is ripe
for re-vamping). Behavior only observed on restarts.
Problem found by, and initial patch from, Henri Kemppainen (thanks!),
though ever so slightly different one applied.
