https://bugs.freedesktop.org/show_bug.cgi?id=109246
--- Comment #26 from OlliC ---
Same problem here. Just switched from a Nvidia GTX 1050Ti to Radeon RX 590 on
Fedora 30 using standard Gnome Desktop.
Using one Benq XL2430 via Displayport and one Benq BL2480T via HDMI.
Monitors won't go to sle
https://bugs.freedesktop.org/show_bug.cgi?id=111481
Bug ID: 111481
Summary: AMD Navi GPU frequent freezes on both Manjaro/Ubuntu
with kernel 5.3 and mesa 19.2 -git/llvm9
Product: DRI
Version: unspecified
Hardware: x86-64 (A
Hi Chris,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.3-rc5 next-20190823]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commit
Quoting Koenig, Christian (2019-08-24 20:04:43)
> Am 24.08.19 um 15:58 schrieb Chris Wilson:
> > In order to allow dma-fence-array as a generic container for fences, we
> > need to allow for it to contain other dma-fence-arrays. By giving each
> > dma-fence-array construction their own lockclass, w
Am 24.08.19 um 15:58 schrieb Chris Wilson:
> In order to allow dma-fence-array as a generic container for fences, we
> need to allow for it to contain other dma-fence-arrays. By giving each
> dma-fence-array construction their own lockclass, we allow different
> types of dma-fence-array to nest, bu
The pull request you sent on Sat, 24 Aug 2019 15:22:55 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-08-24
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bc67b17eb91ea6a2b6d943bb64cde8d1438a11ec
Thank you!
--
Deet-doot-dot, I am a bot.
https://k
From: Wei Hu Sent: Wednesday, August 21, 2019 4:59 AM
>
> > From: Michael Kelley
> > Sent: Monday, August 19, 2019 6:41 AM
> > To: Wei Hu ; rdun...@infradead.org; shc_w...@mail.ru;
>
> > > - msg.dirt.rect[0].x1 = 0;
> > > - msg.dirt.rect[0].y1 = 0;
> > > - msg.dirt.rect[0].x2 = info->var.xres;
>
On 8/23/19 7:34 PM, Brendan Higgins wrote:
## TL;DR
This revision addresses comments from Shuah by fixing a couple
checkpatch warnings and fixing some comment readability issues. No API
or major structual changes have been made since v13.
## Background
This patch set proposes KUnit, a lightwei
https://bugs.freedesktop.org/show_bug.cgi?id=111077
Matt Turner changed:
What|Removed |Added
CC||matts...@gmail.com
--- Comment #18 from M
On Fri, Aug 23, 2019 at 08:47:47AM +, Peter Rosin wrote:
> +++ b/drivers/video/fbdev/core/fbcon.c
> +++ b/drivers/video/fbdev/core/fbmem.c
> @@ -56,6 +56,9 @@ EXPORT_SYMBOL(num_registered_fb);
> bool fb_center_logo __read_mostly;
> EXPORT_SYMBOL(fb_center_logo);
>
> +unsigned int fb_logo_co
Hi Sam,
On Sat, Aug 24, 2019 at 11:54:21AM +0200, Sam Ravnborg wrote:
> On Fri, Aug 23, 2019 at 10:32:44PM +0300, Laurent Pinchart wrote:
> > Add a type field to the drm_panel structure to report the panel type,
> > using DRM_MODE_CONNECTOR_* macros (the values that make sense are LVDS,
> > eDP, D
In order to allow dma-fence-array as a generic container for fences, we
need to allow for it to contain other dma-fence-arrays. By giving each
dma-fence-array construction their own lockclass, we allow different
types of dma-fence-array to nest, but still do not allow on class of
dma-fence-array to
A preliminary set of tests to exercise the basic dma-fence API on top of
struct dma_fence_array.
Signed-off-by: Chris Wilson
---
drivers/dma-buf/Makefile | 3 +-
drivers/dma-buf/selftests.h | 1 +
drivers/dma-buf/st-dma-fence-array.c | 392 +++
3
Quoting Christian König (2019-08-21 13:31:45)
> @@ -528,20 +352,9 @@ void dma_resv_prune_fences(struct dma_resv *obj)
> dma_fence_put(fence);
> }
>
> - list = dma_resv_get_list(obj);
> - if (!list)
> - return;
> -
> - for (i = 0; i < list->s
homas-Hellstr-m-VMware/drm-ttm-drm-vmwgfx-Have-TTM-support-AMD-SEV-encryption/20190824-043622
config: s390-allmodconfig (attached as .config)
compiler: s390-linux-gcc (GCC) 7.4.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.
https://bugs.freedesktop.org/show_bug.cgi?id=111479
Andre Klapper changed:
What|Removed |Added
Component|General |Two
Product|DRI
Hi Laurent et all.
On Fri, Aug 23, 2019 at 10:32:44PM +0300, Laurent Pinchart wrote:
> Add a type field to the drm_panel structure to report the panel type,
> using DRM_MODE_CONNECTOR_* macros (the values that make sense are LVDS,
> eDP, DSI and DPI). This will be used to initialise the correspond
https://bugzilla.kernel.org/show_bug.cgi?id=204181
--- Comment #44 from Sergey Kondakov (virtuous...@gmail.com) ---
(In reply to Alex Deucher from comment #41)
> (In reply to Sergey Kondakov from comment #40)
>
> >
> > I little bit strange to call 2x1080p on AMD's fancy 5-port GPU (+ possible
>
https://bugzilla.kernel.org/show_bug.cgi?id=204683
Bug ID: 204683
Summary: amdgpu: ring sdma0 timeout
Product: Drivers
Version: 2.5
Kernel Version: 5.3.0-rc5
Hardware: x86-64
OS: Linux
Tree: Mainline
On Fri, Aug 23, 2019 at 10:32:43PM +0300, Laurent Pinchart wrote:
> Instead of requiring all drivers to set the dev and funcs fields of
> drm_panel manually after calling drm_panel_init(), pass the data as
> arguments to the function. This simplifies the panel drivers, and will
> help future refact
On Fri, Aug 23, 2019 at 10:32:42PM +0300, Laurent Pinchart wrote:
> Panels must be initialised with drm_panel_init(). Add the missing
> function call in the panel-raspberrypi-touchscreen.c and
> panel-sitronix-st7789v.c drivers.
>
> Signed-off-by: Laurent Pinchart
Thanks, good to have this done
21 matches
Mail list logo
