| Age | Commit message (Collapse) | Author |
|---|
|
|
|
configurations. We don't want to run thousands of lines of
potentially signal-unsafe code for no particular benefit.
ok deraadt@, matthieu@, oga@
|
|
This hasn't been used for a very, very, very long time, (since before
OpenBSD had dri support, for example) and it causes segfaults on dri
drivers when sigio is disabled. Now we don't need to do context swaps on sigio
nor are we trying to do interrupts in userland (thank fuck for that) this
function can die the death that I intended it to die about two years ago, may it
burn.
The kernel support the the sigio ioctl will be removed in a couple of
weeks to give people time to update (right now it accepts it, then
ignores it).
ok kettenis@, matthieu@.
|
|
attempt to open that first before trying /dev/ttyC[0-7].
This makes X autoconfiguration a tad bit more intuitive on machines
with multiple SBus or UPA framebuffers, where wsdisplay0 isn't the
console. PCI framebuffers are still busted though.
ok matthieu@
|
|
limited to sunffb; others will need to be added to bsd_sbus.c if we start
shipping them.
ok matthieu@, oga@
|
|
The code to add sunffb unconditionally on !solaris for __sparc__
systems is incorrect for openbsd. More specifically, due to interactions
between hardware drivers and wsfb in preinit we can't unconditionally
add wsfb to the list of fallbacks, so we only add wsfb if no other
option was found. Additionally sunffb does not need to be
unconditionally added because the bus probing code will find these
devices already.
So, long story short: make that code chunk conditional on __sparc__ &&
defined(__linux__) instead.
change from !openbsd to __linux__ requested by kettenis@.
Tested by at least myself and stsp@.
ok matthieu@, kettenis@.
|
|
that don't have a separate /dev/xf86. Problem noticed by kettenis@ and krw@
ok kettenis@.
|
|
|
|
|
|
|
|
|
|
building xserver 1.6 with those headers. ok oga@.
|
|
A cleaner fix will be forthcoming, but for now this allows the xserver
to work nicely with the recent kernel vt-switch-on-suspend changes.
ok miod@
|
|
found. Makes xorg.conf-less X work again on sparc64 and macppc systems with
a single display adapter.
ok matthieu@, beck@
|
|
|
|
|
|
|
|
|
|
|
|
Ok todd@, oga@.
|
|
|
|
- don't list the dead i810 driver anymore
- blacklist the poulsbo chipset which isn't supported by
xf86-video-intel. Gives vesa a chance. ok oga@, kettenis@.
|
|
It causes lots of spurious warnings in build logs.
suggestion to make the test gcc >= 3.1 millert@, ok todd@, miod@
|
|
on OpenBSD. It will be added by sparcDriverName() if a ffb card
is present.
|
|
I had to disable its build during xserver 1.6 development because it
wasn't building for a while. But all problems are now fixed. ok todd@.
|
|
by my xserver 1.6 merge. noticed by oga@
|
|
was found. This is done in the caller already.
While there change to a switch() construct to prepare for potential
future drivers addition.
|
|
|
|
checking the list), this allows drm to work in -keepPriv situations.
This diff has been in my tree awaiting proper testing for months, now
i'm sure it works correctly in it goes.
ok matthieu@ an aeon ago.
|
|
|
|
|
|
it possible to run X without a configuration file on (some) sparc64 machines
and perhaps other machines that use wscons(4) frame buffers.
ok matthieu@
|
|
|
|
Change kdrive's default configuration too.
|
|
|
|
|
|
|
|
|
|
|
|
top of the scope. this time found by sparc.
|
|
|
|
tested by stsp@, david@, form@, ckuethe@, oga@. thanks.
|
|
- 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)
|
|
|
