xt part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160528/4d545930/attachment.html>
Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2.
Cheers,
-ilia
On Sat, May 28, 2016 at 4:51 PM, Andy Lutomirski wrote:
> I have the signed firmware (I think) and I'm running a fresh 4.6
> kernel. I got an image to show up briefly, rendering the Fedora
> sign-in scre
On Sat 2016-05-28 12:12:06, Pavel Machek wrote:
> Hi!
>
> It looks like redshift stopped working. Even pretty crazy settings
> have no visible effect:
>
> pavel at amd:~$ redshift -O 1500 -g 6.6:6.6:6.6
> Using method `randr'.
> pavel at amd:~$ redshift -x
> Using method `randr'.
> pavel at amd:~
https://bugzilla.kernel.org/show_bug.cgi?id=88861
--- Comment #24 from Wilfried Klaebe ---
Oops, fixed (and double-checked) that email issue. Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160528/797b91e0/attachment.html>
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160528/9f0ea386/attachment.html>
amdkfd need to destroy the debug manager in case amdkfd's notifier
function is called before the unbind function, because in that case,
the unbind function will exit without destroying debug manager.
Signed-off-by: Oded Gabbay
CC: Stable
---
drivers/gpu/drm/amd/amdkfd/kfd_process.c | 10 +++
When unbinding a process from a device (initiated by amd_iommu_v2), the
driver needs to make sure that process still exists in the process table.
There is a possibility that amdkfd's own notifier handler -
kfd_process_notifier_release() - was called before the unbind function
and it already removed
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160528/ed66ce51/attachment-0001.html>
was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160528/934ef1b6/attachment.html>
Mordor screenshot
description||
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160528
just noticed that, in include/uapi/drm/, there are three header
files:
* armada_drm.h
* etnaviv_drm.h
* omap_drm.h
that are not referenced in the corresponding Kbuild file. is there any
rationale for this? in general, is there *any* reason for header files
under include/uapi/ to not be mention
Hi Peter,
On Fri, May 27, 2016 at 11:31:23PM +0200, Peter Wu wrote:
> On Fri, May 27, 2016 at 02:01:39PM +0100, Emil Velikov wrote:
> > On 24 May 2016 at 23:53, Peter Wu wrote:
[snip]
> > > @@ -273,14 +296,14 @@ static bool nouveau_dsm_detect(void)
> > > vga_count++;
> > >
> > >
I have the signed firmware (I think) and I'm running a fresh 4.6
kernel. I got an image to show up briefly, rendering the Fedora
sign-in screen at something like one frame per ten seconds. But then
I got all kinds of garbage, and I see:
[ 719.300820] nouveau :09:00.0: disp: outp 04:0006:0f4
Hi!
It looks like redshift stopped working. Even pretty crazy settings
have no visible effect:
pavel at amd:~$ redshift -O 1500 -g 6.6:6.6:6.6
Using method `randr'.
pavel at amd:~$ redshift -x
Using method `randr'.
pavel at amd:~$ uname -a
Linux amd 4.6.0 #47 SMP Fri May 27 12:07:10 CEST 2016 x86
https://bugzilla.kernel.org/show_bug.cgi?id=88861
--- Comment #23 from Lukas Wunner ---
I've e-mailed Bruno Prémont, author of 4eebd5a4e7269, and cc'ed
platform-driver-x86:
http://www.spinics.net/lists/platform-driver-x86/msg08889.html
I've also cc'ed you but your e-mail address isn't working,
On Fri, 20 May 2016, Scot Doyle wrote:
> On Fri, 20 May 2016, Jeremy Kerr wrote:
> > >Then looks there are two fix patches acked & tested:
> > >
> > > - the patch in this thread
> > > - another one "[PATCH] tty: vt: Fix soft lockup in fbcon cursor
> > >blink timer."
> > > https://lkml.org/lkml/2016
On Thu, 19 May 2016, Scot Doyle wrote:
> Two systems are locking on boot [1] because ops->cur_blink_jiffies
> is set to zero from vc->vc_cur_blink_ms.
>
> Ignore such invalid intervals and log a warning.
>
> [1] https://bugs.launchpad.net/bugs/1574814
>
> Suggested-by: David Daney
> Signed-off-
On Tue, 17 May 2016, David Daney wrote:
> From: David Daney
> We are getting somewhat random soft lockups with this signature:
>
> [ 86.992215] [] el1_irq+0xa0/0x10c
> [ 86.997082] [] cursor_timer_handler+0x30/0x54
> [ 87.002991] [] call_timer_fn+0x54/0x1a8
> [ 87.008378] [] run_timer_sof
Hi Sergei,
Thank you for the patch.
On Friday 29 Apr 2016 00:05:33 Sergei Shtylyov wrote:
> Now that we have the TCON encoder driver, we can start enabling TCON support
> for the R-Car SoCs. We have only tested the code on R8A7794 so far, so
> let it be the first supported SoC...
Please also
Hi Sergei,
Thank you for the patch.
On Friday 29 Apr 2016 00:03:29 Sergei Shtylyov wrote:
> Renesas R-Car SoCs include the timing controller (TCON) that can directly
> drive LCDs. It receives the H/VSYNC, etc. from the Display Unit (DU) and
> converts them to the set of signals that a LCD p
21 matches
Mail list logo
