Age | Commit message (Collapse) | Author |
|
This fixes glReadPixels failure on single-channel 915GM, as the software code
for readpixels was actually the only code in the driver doing tiling against
these buffers (everything else says "rely on fence registers", since the 2D
blits don't have a "don't rely on fence registers" option).
(cherry picked from commit 9a5082d2920c1a212fe935b5a093013e8035c321)
|
|
Yes, it would be nice to do something other than crash here.
Signed-off-by: Keith Packard <keithp@keithp.com>
(cherry picked from commit 7736b65be4fb4d5c59d7aedb1e64da976bb10ae9)
|
|
uxa_prepare_access may fail to map the pixmap into user space. Recover from
this without crashing.
Signed-off-by: Keith Packard <keithp@keithp.com>
(cherry picked from commit 632f816c72cb4b48b690fd92d1cc1d5a9c9285c7)
|
|
These two paths allocate a number of objects directly.
Signed-off-by: Keith Packard <keithp@keithp.com>
(cherry picked from commit 90b28a56553d809374fa6d9b9529b7a8b583488c)
|
|
(cherry picked from commit 59b0fbb9be880d489374b141f818948a2721a2ef)
|
|
The API should be stable at this point, and we don't want to allow mistakes.
|
|
|
|
This fixes glReadPixels failure on single-channel 915GM, as the software code
for readpixels was actually the only code in the driver doing tiling against
these buffers (everything else says "rely on fence registers", since the 2D
blits don't have a "don't rely on fence registers" option).
|
|
Yes, it would be nice to do something other than crash here.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
uxa_prepare_access may fail to map the pixmap into user space. Recover from
this without crashing.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
These two paths allocate a number of objects directly.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
This eliminates the separate i830_allocate_memory_tiled function which means
that all memory objects will have tiling parameters set correctly.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
This fixes VT switch issue with UXA after Eric's
aae4008096399a0e84abc7c016b35092caf9db25 on 2D side.
(cherry picked from commit 1f61e97904dfe5f8c08bb9f284cfdfe878f7e541)
|
|
Since we don't perform any synchronization with the kernel on these regs, we
could race with the kernel to write stale values and end up not having vblank
interrupts enabled when somebody was waiting on one.
(cherry picked from commit 830bf916724afd21b7947f797c22a8c8aab7a0a4)
|
|
This fixes VT switch issue with UXA after Eric's
aae4008096399a0e84abc7c016b35092caf9db25 on 2D side.
|
|
(cherry picked from commit e6479f96e5d8da39fcbb5376c4a66a1f924ec4e4)
|
|
Because of how fallbacky the uxa rendering core is, and our inability (without
wfb in userland or page faulting in the kernel) to tell the kernel just where
we're going to fall back, the clflush overhead can become outrageous, for
example with emacs and xcompmgr. Instead of using drm_intel_bo_map, pin the
buffer and do the fallback to the aperture mapping. This gets us the bad old
performance that fb is designed for, instead of bad new performance.
(cherry picked from commit aae4008096399a0e84abc7c016b35092caf9db25)
|
|
Since we don't perform any synchronization with the kernel on these regs, we
could race with the kernel to write stale values and end up not having vblank
interrupts enabled when somebody was waiting on one.
|
|
(cherry picked from commit 3544bbe22d8cf2640289e1e4febe755a47f26631)
|
|
(cherry picked from commit 8464fc285d7b22fd45b7af616fd52aa15e16638a)
|
|
(cherry picked from commit c1dde7ac06ce6470c74198b2560ee67d28fb0aea)
|
|
(cherry picked from commit 75799d2834be84b016391ec95b221df32380e3e7)
|
|
With batch flush notify vertex buffer will be unreferenced,
so don't count it in later aperture check. Also adding
uninitialized vertex buffer check in batch flush notify.
(cherry picked from commit cfaaf6af777ad8e56da5a077bdc01f4f2d7bc4d6)
|
|
We can't do phy address allocations, need kernel support for this.
Signed-off-by: Dave Airlie <airlied@redhat.com>
(cherry picked from commit b710a688a7383df320f9d4e765b48331310a4d1d)
|
|
Signed-off-by: Dave Airlie <airlied@linux.ie>
(cherry picked from commit 649374b88b330838133d78be1953ce8b18ddd2c6)
|
|
(cherry picked from commit 408f7139354a942f29334795b5480a0b6bb6142a)
|
|
(cherry picked from commit 6b9f421b792c701e909d81ae2b6e6a47fb069b0b)
|
|
(cherry picked from commit a320541e51818833a6a445707835fbf70e9babd4)
|
|
|
|
|
|
|
|
This should be a noop. If it wasn't a noop, it means that on pre-g33 chipsets
we were spamming some data into a page of system memory because we used a
virtual instead of a physical address. It was also supposed to not work when
we submit it from a batchbuffer, as we have been doing for some time now.
This code has existed since about the beginning of the driver's existence,
with no justification.
|
|
|
|
|
|
|
|
|
|
|
|
With batch flush notify vertex buffer will be unreferenced,
so don't count it in later aperture check. Also adding
uninitialized vertex buffer check in batch flush notify.
|
|
We can't do phy address allocations, need kernel support for this.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
Signed-off-by: Dave Airlie <airlied@linux.ie>
|
|
|
|
For broken hardware/bios with incorrect ACPI LID state,
there's machine that can not be fixed in ACPI way, customed
DSDT that reprogram _LID method to read EC state. Although
this is ACPI issue, this quirk can be used to work around that.
|
|
|
|
|
|
For #19115, the root cause is avi_if.u.avi.PR in
i830_sdvo_set_avi_infoframe() belongs to element for
interlaced mode based on CEA_861B, but currently we
don't support interlaced mode. So it should be set as 0.
(cherry picked from commit e38fd84fcccc18284b649a60b4cfd8e24eaf059d)
|
|
(cherry picked from commit 74bc420940de4ed02705211ddebbc4033c032242)
|
|
drmOpen by name only works on linux after falling back to groping around
in /proc. This doesn't work on other OS.
Signed-off-by: Robert Noland <rnoland@2hip.net>
(cherry picked from commit ed267072db7c58ee16a458fd3dc24ce3a2d0061d)
|
|
This avoids prepare/finish_access_gc overhead when we're not changing things
(since GCTile is already handled) and get us the RW flag for the prepare on
of the stipple pixmap so thing will be synced correctly.
(cherry picked from commit ecdd706873c1f990f4a78fbaecf7380411edabcd)
|
|
For #19115, the root cause is avi_if.u.avi.PR in
i830_sdvo_set_avi_infoframe() belongs to element for
interlaced mode based on CEA_861B, but currently we
don't support interlaced mode. So it should be set as 0.
|