| Age | Commit message (Collapse) | Author |
|---|
|
module version early, in order to properly limit the framebuffer size
when a module that doesn't support the new map is loaded. That will
improve backward compatibility. I also made the minimum required kernel
module version 1.3 which hopefully shouldn't be a problem for anybody,
and cleaned up the ordering in which we test for DRM version to enable
features
|
|
Bugzilla #5766 <https://bugs.freedesktop.org/show_bug.cgi?id=5766> Patch
#4636 <https://bugs.freedesktop.org/attachment.cgi?id=4636>
- Acknowledge that RN50 only has one CRTC, and use this to distinguish it
from RV100.
- Fix detection of RN50 memory type and bus width.
- Model RN50 memory bandwidth limits by capping the pixel clock range based
on memory clock, bpp and memory bus width. (ATI Technologies Inc.)
|
|
moving all the accel and card members into the driver ptr, filling in
the exa_major/ exa_minor fields, and always using LoadSubModule so we
can check the module version up front. Only tested on ATI.
|
|
OpenGL textures with EXA.
|
|
the function works in Kb not bytes... Ooops.
|
|
and also limit the CPU accessible memory to the size of the PCI BAR
size (yeah, it was passed to the driver, I just got blind for a while
it seems)
|
|
aligned to its own size. Also add back limit of 128Mb of mapped fb
space for now until I fully sort out what's up with dual function
cards. I would really need to access the PCI BAR sizes here but that
information seem to be missing from the PCI info passed to the driver.
|
|
ati wrapper too (probably not required for it to work as everything
should default to radeon anyway there).
|
|
before XAAInit(), which breaks ShadowFB.
|
|
entries which probably don't really exist (cancelled cards and such),
leave them as-is. Fix the name of some entries, mostly based on the
.inf file of the newest catalyst driver. Use own family id for rv410
and rs400, though there is no different code (yet?).
|
|
detects available & accessible video memory and initializes the card
internal memory map. Along the way, I re-ordered some of the stuffs in
pre-init in order to remove some dodgy codepath, fixed various init,
exit and vt switch issues, and overall made the driver more robust. The
full memory map fix requires an updated DRM. The X driver no longer
tries to position the AGP aperture, this becomes entirely DRM
responsibility.
|
|
addresses are setup, thus causing the card to try to bus master over
the system bus to some stale location (usually 0 but could depend on
whatever was used before X). Remove that useless init bit, and always
setup some good enough engine source & destination pointers in case we
have some other spurrious engine activity going on.
|
|
<john@deater.net>
|
|
[ax]8b8g8r8 pict formats not being supported on r200, but no other
issues.
|
|
1, fixing modesetting issues.
|
|
|
|
so we don't crash when trying to use it later (such as in
RADEONFreeRec).
|
|
|
|
driver version number.
|
|
|
|
(Eric Anholt)
|
|
|
|
|
|
|
|
|
|
|
|
resulted in whining at runtime about the visual not being supported.
|
|
|
|
|
|
|
|
which may or may not have had a negative impact on stability with R300
class cards.
|
|
RADEONDGAInit() even if EXA is enabled; the problematic DGA
acceleration hooks are already disabled in that case.
This fixes DGA issues such as DGA mouse (typically used by games in
fullscreen mode) not working.
Fix suggested by Eric Anholt.
|
|
segfault with MergedFB and EXA enabled and HW cursor temporarily
disabled.
|
|
attachment #3689 (http://bugs.freedesktop.org/attachment.cgi?id=3689)
Fix HW cursor getting silently disabled with EXA.
|
|
|
|
driver if CRT2Position not specified in xorg.conf
<http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6325220>
(Stuart Krietman - Sun Microsystems)
|
|
|
|
the clients to get access to a secure area of framebuffer.
|
|
|
|
|
|
|
|
radeon_commonfuncs.c \
radeon_exa_render.c \
radeon_exa_funcs.c \
|
|
the function (the code above will cause pixmap cache to be freed and
copied around, and these functions must be called after that otherwise
pixmap damage will occur). May be related to #4440, #4456 (unclear if
these setups involve 3d apps)
|
|
coordinates rather than integers.
|
|
stubs from drivers, comment the non-empty ones.
|
|
Include "compiler.h" to define __inline__ on non-gcc compilers
|
|
hook so we can upload a subset of a pixmap, and convert the current
drivers to respect that. Use this support to directly UploadToScreen in
exaGlyphs, providing a 47.4% +/-2.4% decrease in wall time for ls -lR
programs/Xserver in an antialiased gnome-terminal on an M6 (n=3, caches
hot). I would have bumped major version, only I can't tell what the
EXA_VERSION_* is supposed to be doing as opposed to the module version.
|
|
RADEONHostDataBlit.
- Disable the shortcut for switching from 3d to 3d in radeon_exa.c. It
appears that we do need the cache flush here, thought it's not clear
why. Disable the 2d to 2d shortcut while here, since I'm unsure of what
we're doing. Exposed by the following bit:
- Bug #4485: Add a new routine, exaGlyphs, to handle font drawing. Glyphs
were being accumulated in from non-migratable scratch pixmaps, causing
the destination pixmap to move towards screen but the migration
necessary for source never to happen, leading to abysmal performance.
Instead, copy the scratch glyph data into a real pixmap first, then
composite from that into the destination, allowing for migration. time
ls -lR from programs/Xserver showed 26.9% (+/- 6.3%) decrease in wall
time (n=3).
- Create exaDrawableUse* wrapping exaPixmapUse*, but which are aware of
windows needing backing store. Makes migration code prettier, and
ensures that composited windows will be migrated as normal when we turn
off cw for EXA. (issue brought up by keithp)
|
|
allow for PCI/AGP/PCIE cards. Set PCI gart allocation to only happen on
PCIE cards. Add Radeon PCIE card detection using capability bits.
|
|
cards. It has been implicated in hanging at least r300s and some r100s,
and seemed to be the cause of some bad rendering for me.
|
