Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Hardcode the values from a working fglrx run, this works for me now
I've no idea what it might do for anyone else
|
|
I've no idea why or what this does.
|
|
|
|
|
|
|
|
Don't needlessly turn the HW cursor on/off in RADEONLoadCursor*().
Besides cleaning up the code, this semms to avoid some HW cursor related 3D
lockups, see https://bugs.freedesktop.org/show_bug.cgi?id=10815 . My best
guess is that this is because the engine is now always idled before touching
the CRTC registers.
|
|
It can be enabled at runtime by increasing the log verbosity level.
Also change the prefix from (**) to (II) to make grepping the log file for
defaults overridden by xorg.conf more useful again.
Turn some MC related debugging output into normal informational output as it's
useful for recognizing corner cases that can cause stability issues.
|
|
|
|
- logic in RADEONUnblank() was wrong
- Calling RADEONSetupConnectors() on second instance screwed up the port info
- still seem to be HW cursor issues with zaphod mode
|
|
This attempts to keep it inside the 32-bit limit when multiplying things out
later in the randr tree.
Let me know if I screwed this up..
|
|
I noticed fglrx has DDC for the panel in the rs480 laptop, however radeon
didn't pick it up, so I valgrinded fglrx and spotted 0x1a0/0x1a4 accesses
I actually noticed this before from the BIOS but never figured it out.
So now I get DDC from the LCD on this laptop.
|
|
I noticed fglrx has DDC for the panel in the rs480 laptop, however radeon
didn't pick it up, so I valgrinded fglrx and spotted 0x1a0/0x1a4 accesses
I actually noticed this before from the BIOS but never figured it out.
So now I get DDC from the LCD on this laptop.
|
|
|
|
|
|
Due to the hardware layout RMX ddc_mode has to be set.
If ddc_mode is set, RADEONValdiateFPModes() shouldn't be called.
Bugzilla #10620 (3).
|
|
According to Lisa Wu, this is correct regarding the VESA EEDID standard.
Bugzilla #10620 (2), original patch by Lisa Wu @ATI
|
|
Some scans used to only check every second entry, some stopped at the entry
before the last entry.
Bugzilla #10620 (1), original patch by Lisa Wu @ATI
|
|
If the secondary head isn't found (Monitor unplugged etc.) but MergedFB
is configured, the driver segfaults because it tries to access the mode
list private structures, which are not filled in.
|
|
|
|
Thanks to Matthew Garrett and Ubuntu for the hw loan to get this working.
Still no 3D driver support but at least you should get CP acceleration for
2D now.
|
|
This makes sure all modes of both CRTCs will be available by default with
MergedFB.
|
|
This makes sure mode lists will always be sorted from larger to smaller.
|
|
|
|
|
|
|
|
Fixes https://bugs.freedesktop.org/show_bug.cgi?id=10442 .
|
|
|
|
|
|
|
|
when IsSecondary is true, crtc1 is NULL
Noticed by Sverre Froyen.
|
|
|
|
atimisc is PCI-only now, we can get the chip name with xf86TokenToString().
|
|
There is no need to override pATI->ChipRevision for GX/CX, as it is only
reported with a printf.
|
|
atimisc is PCI-only now, so we only need to scan the PCI space.
|
|
|
|
|
|
Subdrivers are now loaded from the wrapper Probe function rather than at screen
creation time.
The wrapper Identify callback only prints chip families now, chip lists are
printed when a subdriver is loaded. This also avoids duplication of subdriver
Identify callbacks.
Unknown radeons should still get a list of known radeon and then probe fails...
Probe for atimisc last to avoid needless loading in most cases (r128, radeon).
|
|
We don't automatically require bumped minor versions.
|
|
In particular, don't sync again after accelerated DownloadFromScreen, which
syncs implicitly. This avoids calling into the kernel when it's not necessary,
which can be relevant in some situations.
|
|
|
|
Don't flush indirect buffer in BlockHandler; it's done in LeaveServer.
Also set the EXA engine mode to unknown only at the end.
|
|
There have been several reports of stability issues with things like the
xscreensaver hack hypercube.
|
|
Walk the SAREA texList and bump the age of every active object, so their owners
will consider them kicked out when they grab the HW lock next time.
|
|
|
|
|
|
|
|
|