https://bugzilla.kernel.org/show_bug.cgi?id=194761
--- Comment #80 from Jean Delvare (jdelv...@suse.de) ---
I tested the patch from comment #78 and unfortunately I have to report that it
doesn't fix the problem for me, checkerboard effect is still present.
Nevertheless these cleanups look good so
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: 9394a345b337d38d55ff027f25147c3a7360d320
commit: db1fc97ca0c0d3fdeeadf314d99a26188438940a [410/417] dma-buf/sync_file:
Allow multiple sync_files to wrap a single dma-fence
reproduce: make htmldocs
All warnings (new ones prefixed by
On 17-07-29 13:53:10, Daniel Stone wrote:
Hi Ben,
On 26 July 2017 at 19:08, Ben Widawsky wrote:
+ } else if (INTEL_GEN(dev_priv) >= 9) {
intel_primary_formats = skl_primary_formats;
num_formats = ARRAY_SIZE(skl_primary_formats);
- modifiers =
Hi Philippe,
On 07/17/2017 01:10 PM, Philippe CORNU wrote:
The pixel clock gets enabled early during init, since it's required
in order to read registers. This pixel clock must be disabled if
errors during this init phase.
This patch was pulled in to drm-misc-next, but it lacks your Sign-off.
https://bugs.freedesktop.org/show_bug.cgi?id=101946
--- Comment #19 from Robin ---
I've found that my test cases only trigger the PCI drivers'
amdgpu_pci_remove and amdgpu_pci_probe functions.
Adding the new shutdown function call amdgpu_device_shutdown(adev); to the
amdgpu_pci_remove function d
Hi Daniel,
Thanks for your reply.
Currently I am using connector type 'Unknown' , and functionally it serves my
need.
Intention for sending this patch is that userspace tools should recognize SDI
drivers as SDI only.
Also, I see there are number of 'SDI' drivers getting developed 'under the
hoo
On Fri, Jul 28, 2017 at 2:13 AM, Christian König
wrote:
> Am 28.07.2017 um 03:43 schrieb Alex Deucher:
>>
>> On Tue, Jul 25, 2017 at 5:47 PM, Kees Cook wrote:
>>>
>>> As done for vega10 in commit 3ddd396f6b57 ("drm/amd/powerplay: Use
>>> designated initializers") mark other tableFunction entries
From: Gustavo Padovan
We are going to use timeline_fence_signaled() in a internal function in
the next commit.
Cc: Chris Wilson
Signed-off-by: Gustavo Padovan
---
drivers/dma-buf/sw_sync.c | 138 +++---
1 file changed, 69 insertions(+), 69 deletions(-)
Den 23.07.2017 21.16, skrev Noralf Trønnes:
This adds defaults for the drm_driver.dumb_destroy and
drm_driver.dumb_map_offset callbacks as discussed with Daniel.
vmwgfx is the only driver that doesn't use drm_gem_dumb_destroy().
vgem
vgem changes behaviour after this, because it didn't ha
https://bugs.freedesktop.org/show_bug.cgi?id=101881
--- Comment #5 from Rafael Ristovski ---
I can confirm a very similar issue on my SI Cape Verde (HD8850M GCN1.0) using
the amdgpu driver with mesa. It happens even if I compile mesa's `xdemos` with
-m32 in which case most of the binaries produce
https://bugs.freedesktop.org/show_bug.cgi?id=101484
Lucas Francesco changed:
What|Removed |Added
CC||lucas.francesc...@gmail.com
--- Comme
https://bugs.freedesktop.org/show_bug.cgi?id=101946
--- Comment #20 from Robin ---
Created attachment 133132
--> https://bugs.freedesktop.org/attachment.cgi?id=133132&action=edit
Brute-force fix, resets sdma every init
After much trial and error, I've found this approach to work.
Every hw_init
https://bugs.freedesktop.org/show_bug.cgi?id=101631
Denys changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hi Maarten,
On Wednesday 26 Jul 2017 14:53:33 Laurent Pinchart wrote:
> On Wednesday 19 Jul 2017 16:39:16 Maarten Lankhorst wrote:
> > for_each_obj_in_state is about to be removed, so use the correct new
> > iterator macros.
> >
> > Also look at new_plane_state instead of plane->state when lookin
From: Gustavo Padovan
We found this bug in the sw_sync so adding a test case to prevent it to
happen in the future.
Cc: Shuah Khan
Cc: linux-kselft...@vger.kernel.org
Signed-off-by: Gustavo Padovan
---
To be applied after the TAP13 convertion patches.
---
tools/testing/selftests/sync/sync_fe
Page flips can take more than one vertical blanking to complete if
arming the page flips races with the vertical blanking interrupt.
Waiting for one vblank to complete the atomic commit in the commit tail
handler is thus incorrect, and can lead to framebuffers being released
while still being scann
Den 27.07.2017 11.58, skrev Arnd Bergmann:
The new RePaper driver uses the thermal subsystem, and fails to link
when it is built-in but thermal is a loadable module:
drivers/gpu/drm/tinydrm/repaper.o: In function `repaper_probe':
repaper.c:(.text+0x540): undefined reference to `thermal_zone_get
When stopping the CRTC the driver must disable all planes and wait for
the change to take effect at the next vblank. Merely calling
drm_crtc_wait_one_vblank() is not enough, as the function doesn't
include any mechanism to handle the race with vblank interrupts.
Replace the drm_crtc_wait_one_vblan
On 2017-07-23 12:16, Noralf Trønnes wrote:
> This driver can use the drm_driver.dumb_destroy and
> drm_driver.dumb_map_offset defaults, so no need to set them.
>
> Cc: Stefan Agner
> Cc: Alison Wang
> Signed-off-by: Noralf Trønnes
Acked-by: Stefan Agner
--
Stefan
> ---
> drivers/gpu/drm/fs
When implementing support for interlaced modes, the driver switched from
reporting vblank events on the vertical blanking (VBK) interrupt to the
frame end interrupt (FRM). This incorrectly divided the reported refresh
rate by two. Fix it by moving back to the VBK interrupt.
Fixes: 906eff7fcada ("d
Hello,
The recent changes to the rcar-du driver to fix a page flip handling race
condition changed the order of which vblanks and page flips are handled,
resulting in incorrect timestamps being reported in the vblan events. Correct
this by handling vblank events in the same completion handler as p
Hi,
On 26 July 2017 at 19:08, Ben Widawsky wrote:
> +static const uint64_t skl_plane_format_modifiers_noccs[] = {
> + I915_FORMAT_MOD_Yf_TILED,
> + I915_FORMAT_MOD_Y_TILED,
> + I915_FORMAT_MOD_X_TILED,
> + DRM_FORMAT_MOD_LINEAR,
> + DRM_FORMAT_MOD_INVALID
> +};
> +
>
https://bugs.freedesktop.org/show_bug.cgi?id=101969
Bug ID: 101969
Summary: Massive graphics corruption with World of Warcraft
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=94410
--- Comment #3 from Thomas Kowaliczek ---
Created attachment 133122
--> https://bugs.freedesktop.org/attachment.cgi?id=133122&action=edit
Schreenshot1
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=94410
--- Comment #4 from Thomas Kowaliczek ---
Created attachment 133123
--> https://bugs.freedesktop.org/attachment.cgi?id=133123&action=edit
Screenshot2
--
You are receiving this mail because:
You are the assignee for the bug.___
Hi Chris,
2017-07-28 Chris Wilson :
> Up until recently sync_file were create to export a single dma-fence to
> userspace, and so we could canabalise a bit insie dma-fence to mark
> whether or not we had enable polling for the sync_file itself. However,
> with the advent of syncobj, we do allow u
Hi Ben,
On 26 July 2017 at 19:08, Ben Widawsky wrote:
> + } else if (INTEL_GEN(dev_priv) >= 9) {
> intel_primary_formats = skl_primary_formats;
> num_formats = ARRAY_SIZE(skl_primary_formats);
> - modifiers = skl_format_modifiers;
> +
From: Gustavo Padovan
If userspace already dropped its own reference by closing the sw_sync
fence fd we might end up in a deadlock where
dma_fence_is_signaled_locked() will trigger the release of the fence and
thus try to hold the lock to remove the fence from the list.
dma_fence_is_signaled_loc
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #19 from lef...@gmail.com ---
I can confirm this happens with radeonsi too
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@li
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #20 from Shmerl ---
(In reply to Lennard from comment #19)
> I can confirm this happens with radeonsi too
Well, most previous reports were about radeonsi.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=101946
--- Comment #18 from Robin ---
Created attachment 133127
--> https://bugs.freedesktop.org/attachment.cgi?id=133127&action=edit
Logging shutdown function
I've modified the patch to include info messages. The code path is never
executed in my t
https://bugs.freedesktop.org/show_bug.cgi?id=94410
--- Comment #5 from Thomas Kowaliczek ---
Screenshost are from version 4.17 after the editor startup freezed my desktop.
Only mouse worked.
--
You are receiving this mail because:
You are the assignee for the bug.___
From: Kieran Bingham
The driver recently switched from handling page flip completion in the
DU vertical blanking handler to the VSP frame end handler to fix a race
condition. This unfortunately resulted in incorrect timestamps in the
vertical blanking events sent to userspace as vertical blanking
On Thu, Jul 27, 2017 at 6:43 PM, Alex Deucher wrote:
> On Tue, Jul 25, 2017 at 5:47 PM, Kees Cook wrote:
>> As done for vega10 in commit 3ddd396f6b57 ("drm/amd/powerplay: Use
>> designated initializers") mark other tableFunction entries with designated
>> initializers. The randstruct plugin requi
On Fri, Jul 28, 2017 at 04:23:11PM +0100, Liviu Dudau wrote:
> On Wed, Jul 26, 2017 at 11:27:48AM +0100, Russell King - ARM Linux wrote:
> > On Wed, Jul 26, 2017 at 11:05:39AM +0100, Russell King wrote:
> > > Some ARM platforms do not wire the HDLCD interrupt. Allow hdlcd to
> > > initialise witho
https://bugs.freedesktop.org/show_bug.cgi?id=101881
--- Comment #6 from Rafael Ristovski ---
Also, the llvm issue indeed goes away when adding debug support.
I think this might be related to a race condition caused by recent versions of
gcc.
--
You are receiving this mail because:
You are the a
https://bugs.freedesktop.org/show_bug.cgi?id=101631
Denys changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=101672
--- Comment #19 from MirceaKitsune ---
The freeze still happens with the Performance Enhance BIOS setting turned off,
the crash is not caused by my overclocking settings. It took 2 hours of playing
Minecraft in a row for it to occur again.
I no
https://bugs.freedesktop.org/show_bug.cgi?id=101377
--- Comment #6 from j...@dev1ce.com ---
the problem with this regression to older firmware is that while the kernel
boots, none of the 3D functionality inherent in the new drivers is functional.
I can regress to an older kernel with the newer fir
39 matches
Mail list logo
