Hi Linus,
Not actually back online fully, but I've managed to find a few minutes
to pull in all the fixes that were meant for rc5 but have leaked over.
There are two AGP fixes in here, as well as a bunch of mostly amdgpu
fixes, along with a sun4i build fix, two armada fixes and some tegra
fixes,
https://bugs.freedesktop.org/show_bug.cgi?id=105251
--- Comment #13 from Barry G ---
I upgraded my linux-firmware to 20180606.d114732-1 and it had no affect on the
issue. Still locks running the script with the same dmesg.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105251
--- Comment #12 from Barry G ---
My system (Threadripper, Vega 64) started exhibiting the same issue on 4.17.
It will lock hard for me under IO. I have a custom python script that I run
that does NFS IO off my X550 network card and then
https://bugs.freedesktop.org/show_bug.cgi?id=105251
Barry G changed:
What|Removed |Added
CC||ba...@grussling.com
--- Comment #11 from
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #34 from dwagner ---
(In reply to Doctor from comment #32)
> Just cherry picking the code
> back to the last 4.16 and no problems Heres the working 4.16 . I chased
> this rabbit for awhile and it pops up like the dam wood chuck in
https://bugzilla.kernel.org/show_bug.cgi?id=200499
Michael Straube (straube.li...@gmail.com) changed:
What|Removed |Added
Regression|No |Yes
--
You
https://bugzilla.kernel.org/show_bug.cgi?id=200499
--- Comment #1 from Michael Straube (straube.li...@gmail.com) ---
Created attachment 277361
--> https://bugzilla.kernel.org/attachment.cgi?id=277361=edit
bisect log
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=200499
Bug ID: 200499
Summary: amdgpu: kfd: kgd2kfd_probe failed, Ryzen 2400G
Product: Drivers
Version: 2.5
Kernel Version: 4.18-rc4
Hardware: x86-64
OS: Linux
https://bugs.freedesktop.org/show_bug.cgi?id=107229
--- Comment #2 from Alexander Tsoy ---
(In reply to Alexander Tsoy from comment #0)
> With 4.14 kernels the game process is unkillable so it hangs somewhere
> in the kernel space. With 4.17 kernels it can be killed but this
> takes some time.
On Fri, Jul 13, 2018 at 6:39 AM, Leonard Crestez
wrote:
> The imx6sl soc has gpu_2d and gpu_vg, no 3d support:
>
> etnaviv-gpu 220.gpu: model: GC320, revision: 5007
> etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
>
> The IP blocks seem to be already supported.
>
> Signed-off-by:
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")
This patch map/unmap GEM backing memory to kernel address space
in prepare/cleanup_fb respectively and cache the virtual address
for later use.
Signed-off-by: Haneen Mohammed
---
Changes in v2:
- use vkms_gem_vunmap
drivers/gpu/drm/vkms/vkms_plane.c | 36 ++-
1 file
From 8aded81852666b591624001ec02aa4dc0d8f4cfb Mon Sep 17 00:00:00 2001
From: Sam Ravnborg
Date: Sat, 14 Jul 2018 22:17:18 +0200
Subject: [PATCH 1/1] atmel_lcdfb: support native-mode display-timings
When a device tree set a display-timing using native-mode
then according to the bindings doc this
Pls ignore this.there has a fix:
[PATCH] fbdev/via: fix defined but not used warning
On 2018/7/13 15:56, YueHaibing wrote:
> When CONFIG_PROC_FS isn't set, gcc warning this:
>
> drivers/video/fbdev/via/viafbdev.c:1471:12: warning:
> ‘viafb_sup_odev_proc_show’ defined but not used
This patchset implement CRC debugfs API and add the necessary
infrastructure required to enable to compute and add CRCs entries.
1. add functions to map/unmap buffers to kernel address space.
2. map/unmap buffers in the prepare/cleanup_fb hooks.
3. compute crc using crc32 on the visible portion
Hi David,
The following changes since commit 29dcea88779c856c7dc92040a0c01233263101d4:
Linux 4.17 (2018-06-03 14:15:21 -0700)
are available in the git repository at:
git://git.armlinux.org.uk/~rmk/linux-arm.git drm-armada-fixes
for you to fetch changes up to
Implement the set_crc_source() callback.
Compute CRC using crc32 on the visible part of the framebuffer.
Use ordered workqueue to compute and add CRC at the end of a vblank.
Use appropriate synchronization methods since the crc computation must
be atomic wrt the generated vblank event for a given
On 07/13/2018 12:33 PM, Stefan Agner wrote:
> On 13.07.2018 11:12, Marek Vasut wrote:
>> On 07/13/2018 11:06 AM, Anson Huang wrote:
>> [...]
On 07/13/2018 10:54 AM, Anson Huang wrote:
> As display power domain is combined with lcdif node on some i.MX
> platforms like i.MX6SL,
On 07/13/2018 10:54 AM, Anson Huang wrote:
> As display power domain is combined with lcdif node
> on some i.MX platforms like i.MX6SL, when lcdif driver
> is enabled, the mxsfb_load is called to enable runtime
> pm, and a pair of pm_runtime_get_sync and
> pm_runtime_put_sync are also called, that
The mode fixup code has a nice, logical explanation of what it should
do, but unfortunately it doesn't reflect reality.
For bridges:
* @mode_fixup:
*
* This callback is used to validate and adjust a mode. The paramater
* mode is the display mode that should be
On Wed, Jul 11 2018, Andrew Morton wrote:
> On Wed, 11 Jul 2018 13:51:08 +0200 Daniel Vetter wrote:
>
>> But I still have the situation that a bunch of maintainers acked this
>> and Andrew Morton defacto nacked it, which I guess means I'll keep the
>> macro in drm? The common way to go about
Subclass CRTC state struct to enable storing driver's private
state. This patch only adds the base drm_crtc_state struct and
the atomic functions that handle it.
Signed-off-by: Haneen Mohammed
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/vkms/vkms_crtc.c | 53 ++--
Anson Huang
Best Regards!
> -Original Message-
> From: Marek Vasut [mailto:ma...@denx.de]
> Sent: Friday, July 13, 2018 5:03 PM
> To: Anson Huang ; airl...@linux.ie;
> dri-devel@lists.freedesktop.org; linux-ker...@vger.kernel.org
> Cc: dl-linux-imx
> Subject: Re: [PATCH] drm: mxsfb:
On Fri, 2018-07-13 at 11:12 +0200, Marek Vasut wrote:
> On 07/13/2018 11:06 AM, Anson Huang wrote:
> [...]
> > >
> > > On 07/13/2018 10:54 AM, Anson Huang wrote:
> > > > As display power domain is combined with lcdif node on some i.MX
> > > > platforms like i.MX6SL, when lcdif driver is enabled,
Call atomic_helper_check_plane_state to clip plane coordinates.
Signed-off-by: Haneen Mohammed
---
Changes in v2:
- check for plane_state->visible since we can't handle a disabled
primary plane yet.
drivers/gpu/drm/vkms/vkms_plane.c | 29 +
1 file changed, 29
When CONFIG_PROC_FS isn't set, gcc warning this:
drivers/video/fbdev/via/viafbdev.c:1471:12: warning: ‘viafb_sup_odev_proc_show’
defined but not used [-Wunused-function]
static int viafb_sup_odev_proc_show(struct seq_file *m, void *v)
^
fix this by adding #ifdef around it.
On 07/13/2018 12:39 PM, Stefan Agner wrote:
> On 13.07.2018 12:36, Marek Vasut wrote:
>> On 07/13/2018 12:33 PM, Stefan Agner wrote:
>>> On 13.07.2018 11:12, Marek Vasut wrote:
On 07/13/2018 11:06 AM, Anson Huang wrote:
[...]
>>
>> On 07/13/2018 10:54 AM, Anson Huang wrote:
As display power domain is combined with lcdif node
on some i.MX platforms like i.MX6SL, when lcdif driver
is enabled, the mxsfb_load is called to enable runtime
pm, and a pair of pm_runtime_get_sync and
pm_runtime_put_sync are also called, that will cause
generic power domain driver to disable
On Wed, Mar 28, 2018 at 12:14:45PM +0200, Daniel Vetter wrote:
> On Wed, Mar 28, 2018 at 11:08 AM, Lucas Stach wrote:
> > Am Mittwoch, den 28.03.2018, 09:02 +0200 schrieb Daniel Vetter:
> >> On Tue, Mar 27, 2018 at 01:30:04PM +0200, Michael Grzeschik wrote:
> >> > On Mon, Mar 26, 2018 at
This patch add the necessary functions to map/unmap GEM
backing memory to the kernel's virtual address space.
Signed-off-by: Haneen Mohammed
---
Changes in v2:
- add vkms_gem_vunmap
- use vmap_count to guard against multiple prepare_fb calls on the same
fb
drivers/gpu/drm/vkms/vkms_drv.h |
On 07/13/2018 04:37 PM, NeilBrown wrote:
> On Wed, Jul 11 2018, Andrew Morton wrote:
>
>> On Wed, 11 Jul 2018 13:51:08 +0200 Daniel Vetter wrote:
>>
>>> But I still have the situation that a bunch of maintainers acked this
>>> and Andrew Morton defacto nacked it, which I guess means I'll keep
The imx6sl soc has gpu_2d and gpu_vg, no 3d support:
etnaviv-gpu 220.gpu: model: GC320, revision: 5007
etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
The IP blocks seem to be already supported.
Signed-off-by: Leonard Crestez
Reviewed-by: Lucas Stach
---
On 10/07/18 10:46, Sudeep Holla wrote:
>
> On 09/07/18 08:52, Linus Walleij wrote:
[...]
>
> Still get below warnings, not sure if I need to upgrade my DTC ?
>
> vexpress-v2f-1xv7-ca53x2.dtb: Warning (graph_child_address):
>
On 07/13/2018 11:06 AM, Anson Huang wrote:
[...]
>>
>> On 07/13/2018 10:54 AM, Anson Huang wrote:
>>> As display power domain is combined with lcdif node on some i.MX
>>> platforms like i.MX6SL, when lcdif driver is enabled, the mxsfb_load
>>> is called to enable runtime pm, and a pair of
https://bugs.freedesktop.org/show_bug.cgi?id=105760
--- Comment #46 from Alex Deucher ---
(In reply to Thomas Martitz from comment #45)
>
> If I insert a printk after the pci_set_power_state() succeeds and pci ->
> current_state indicates that gpu is powered on, yet reading from the mapped
>
On Sat, Jul 14, 2018 at 12:31 PM, Takashi Iwai wrote:
> On Sat, 14 Jul 2018 14:03:26 +0200,
> jimqu wrote:
>>
>>
>>
>> 在 2018/7/13 23:07, Takashi Iwai 写道:
>> > On Wed, 11 Jul 2018 13:12:01 +0200,
>> > Takashi Iwai wrote:
>> >> And the forced runtime PM is still an issue, and this would need the
https://bugzilla.kernel.org/show_bug.cgi?id=199585
Jason Hicks (jasz...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #33 from Doctor ---
I think it may be something as stupid as a var too.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #32 from Doctor ---
I ended up due to working on a live dev cd for codexl since all my machines are
memory based and use no magnetic media. Just cherry picking the code back to
the last 4.16 and no problems Heres the working 4.16 .
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #31 from Doctor ---
I got that one too and was able to track the problem down a bit further. Chrome
and video with the gpu enabled will blow it up too. Interesting I was able to
reproduce it consistantly with my rtl8188eu usb driver
40 matches
Mail list logo
