https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #57 from tempel.jul...@gmail.com ---
Instead of my usual DL-DVI display, I connected a Samsung C27H711 via Display
Port. It officially offers 2560x1440 75Hz and the very same flickering issue
occurs.
I suspect the Polaris Windows dri
https://bugzilla.kernel.org/show_bug.cgi?id=201835
Bug ID: 201835
Summary: nouveau :01:00.0: fifo: fault 01 [WRITE] at
0016 engine 15 [CE0] client 01 [HUB/CE0]
reason c2 [] on channel 0 [00ff9a6000 DRM]
Produ
: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-...@kernel-bugs.osdl.org
Reporter: m...@osknowledge.org
Regression: No
/var/log/debug-20181202
https://bugs.freedesktop.org/show_bug.cgi?id=108710
--- Comment #10 from mikhail.v.gavri...@gmail.com ---
Looks like problem was gone after commit 94f371cb7394
In Fedora this is package 4.20.0-0.rc4.git2.1.fc30.x86_64
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=105837
Sherif changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
On Wed, Nov 21, 2018 at 8:55 PM Jonathan Marek wrote:
>
> Controls which of the 8 lanes are used for 6 bit color.
>
> Signed-off-by: Jonathan Marek
> ---
> .../gpu/drm/msm/disp/mdp4/mdp4_lcdc_encoder.c | 22 ---
> 1 file changed, 14 insertions(+), 8 deletions(-)
>
> diff --git a/
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #32 from Shecks ---
(In reply to freedesktop from comment #27)
> OK there seems to be something screwy going on with the amdgpu.dpm option -
> if that's set to 0, it still results in a blank screen. It has to be removed
> entirely fr
On Wed, Nov 21, 2018 at 8:55 PM Jonathan Marek wrote:
>
> This patch allows using drm/msm without qcom display hardware. This is
> especially useful for iMX5 hardware, which has a a2xx GPU but uses the
> imx-drm driver for display.
>
> Signed-off-by: Jonathan Marek
> ---
> v2: added commit messag
Den 30.11.2018 00.58, skrev Eric Anholt:
Daniel Vetter writes:
On Wed, Nov 28, 2018 at 01:52:56PM -0800, Eric Anholt wrote:
Daniel Vetter writes:
On Tue, Nov 27, 2018 at 12:38:44PM -0800, Eric Anholt wrote:
Daniel Vetter writes:
On Mon, Nov 26, 2018 at 04:36:21PM -0800, Eric Anholt wr
https://bugs.freedesktop.org/show_bug.cgi?id=108919
Bug ID: 108919
Summary: Parkitect (Unity Game) dispalys artifacts and black
screens with Vega hardware
Product: Mesa
Version: 18.2
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=108919
--- Comment #1 from Juyas Yove ---
Created attachment 142690
--> https://bugs.freedesktop.org/attachment.cgi?id=142690&action=edit
Another artifact example
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=106617
--- Comment #6 from Sylvain BERTRAND ---
still happening
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://li
https://bugzilla.kernel.org/show_bug.cgi?id=201843
Bug ID: 201843
Summary: Micro-stuttering each second on amdgpu only on
2560x1440
Product: Drivers
Version: 2.5
Kernel Version: 4.19.2-arch1-1-ARCH
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=201843
--- Comment #1 from Oleg Chernovskiy (kairl...@yandex.ru) ---
Created attachment 279799
--> https://bugzilla.kernel.org/attachment.cgi?id=279799&action=edit
No stutter - DOOM 1920x1080
Attacting sample in 1920x1080 without stuttering, same PC,
https://bugs.freedesktop.org/show_bug.cgi?id=108920
Bug ID: 108920
Summary: [AMDGPU][TAHITI XT] linux unable to boot since rc3
rebase
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Bisected:
due to many compilation errors, git say any of the following commit could be
the culprit:
663480d4e1460943de83ef14e86b8d2b0776edc6
971dbfb07e6ab4c5113898df25f39815c867a49c
103fcde3210ae17101bc1c64a78d074d61cf5cf7
85d5f3312d67bf8def41110447d19de3a0665754
0bf89d5dd1ee497df340ce932f0726d499
https://bugs.freedesktop.org/show_bug.cgi?id=108920
--- Comment #1 from Sylvain BERTRAND ---
Bisected:
due to many compilation errors, git say any of the following commit could be
the culprit:
663480d4e1460943de83ef14e86b8d2b0776edc6
971dbfb07e6ab4c5113898df25f39815c867a49c
103fcde3210ae17101bc1
https://bugzilla.kernel.org/show_bug.cgi?id=201843
fin4...@hotmail.com changed:
What|Removed |Added
CC||fin4...@hotmail.com
--- Comment #2
https://bugzilla.kernel.org/show_bug.cgi?id=201843
--- Comment #3 from Oleg Chernovskiy (kairl...@yandex.ru) ---
> I could not see any difference in your pictures.
Okay, please explain what GPU is doing exactly once per second on the graphs
when I look at nothing but the wall in the game?
> AMD
In analogy to drm_default_rgb_quant_range, create
drm_default_colorimetry helper function to determine the default
colorimetry value based on drm_display_mode. Currently there isn't any
standarized way to determine the default color space format.
Signed-off-by: Christoph Manszewski
---
drivers/g
Previouly drivers have their own way of mapping range of
kernel pages/memory into user vma and this was done by
invoking vm_insert_page() within a loop.
As this pattern is common across different drivers, it can
be generalized by creating a new function and use it across
the drivers.
vm_insert_ra
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/video/fbdev/omap2/omapfb/dss/core.c | 16 +++-
1 file changed, 3 insertions(+), 13 deletions(-)
diff --git a/drivers/video/fbdev/omap2/omapfb/dss/core.c
b/drivers/video/fbdev/omap2/omapfb/ds
Hi,
This is about a TV stick called MK808.
Enabled VOP an HDMI for rk3066.
Able to see pinguins at boot.
Found similar bug reports for rk3399.
http://lists.infradead.org/pipermail/linux-rockchip/2018-April/020426.html
http://lists.infradead.org/pipermail/linux-rockchip/2018-April/020427.html
htt
在 2018-11-27二的 15:42 +0800，Icenowy Zheng写道：
> Some SoCs adds a bus clock gate to the Mali Midgard GPU.
>
> Add the binding for the bus clock.
>
> Signed-off-by: Icenowy Zheng
Could anyone have a check on this patchset?
> ---
> Documentation/devicetree/bindings/gpu/arm,mali-midgard.txt | 6
> +
Hello,
This patch series implements a generic helper function, to determine
the default color space format. I've tried to do it in analogy to
an already existing function, but I'am not sure if it is done the right way.
Patch 1 implements the mentioned function
Patch 2 makes use of it in exynos_m
Previouly drivers have their own way of mapping range of
kernel pages/memory into user vma and this was done by
invoking vm_insert_page() within a loop.
As this pattern is common across different drivers, it can
be generalized by creating a new function and use it across
the drivers.
vm_insert_ra
Alpha enable in the pixel format will help in
selecting the blend rule. By keeping alpha enable
to true we are allowing foreground alpha to blend
with the layer. If alpha is don't care, then we
should not allow pixel alpha to be part of blend
equation.
Signed-off-by: Jayant Shekhar
---
drivers/g
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/gpu/drm/vkms/vkms_plane.c: In function 'vkms_prepare_fb':
drivers/gpu/drm/vkms/vkms_plane.c:144:26: warning:
variable 'vkms_obj' set but not used [-Wunused-but-set-variable]
It never used since introduction in commit
8ce1bb0b5337 ("drm/vkms:
Use drm_default_colorimetry helper function to determine the default
colorspace type (ITU-R BT.601 or ITU-R BT.709).
Signed-off-by: Christoph Manszewski
---
drivers/gpu/drm/exynos/exynos_mixer.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/exynos/exynos_m
On Fri, Nov 30, 2018 at 7:26 PM Jarkko Sakkinen
wrote:
>
> On Fri, Nov 30, 2018 at 06:13:50PM -0200, Diego Viola wrote:
> > On Fri, Nov 30, 2018 at 5:30 PM Jarkko Sakkinen
> > wrote:
> > >
> > > In order to comply with the CoC, replace with a hug.
> > >
> > > Signed-off-by: Jarkko Sakkinen
On Tue, Nov 27, 2018 at 10:56:42AM +, Daniel Thompson wrote:
> On Sat, Nov 24, 2018 at 09:17:02AM -0500, Brian Masney wrote:
> > Add a trivial binding for the Texas Instruments LM3630A Backlight Chip.
>
> It's quite unusual for a backlight device to have a trivial binding.
>
> The driver supp
Rob/Brian
On 11/30/2018 08:13 AM, Rob Herring wrote:
> +Dan M
>
> On Fri, Nov 30, 2018 at 7:59 AM Brian Masney wrote:
>>
>> On Tue, Nov 27, 2018 at 10:56:42AM +, Daniel Thompson wrote:
>>> On Sat, Nov 24, 2018 at 09:17:02AM -0500, Brian Masney wrote:
Add a trivial binding for the Texas
On Thu, Nov 29, 2018 at 7:29 PM Luis Chamberlain wrote:
>
> On Wed, Nov 28, 2018 at 11:36:20AM -0800, Brendan Higgins wrote:
> > A number of test features need to do pretty complicated string printing
> > where it may not be possible to rely on a single preallocated string
> > with parameters.
> >
We already have the DEFINE_SHOW_ATTRIBUTE.There is no need to define
such a macro separately,so remove DEFINE_DPU_DEBUGFS_SEQ_FOPS.
Also use DEFINE_SHOW_ATTRIBUTE to simplify some code.
Signed-off-by: Yangtao Li
---
drivers/gpu/drm/armada/armada_debugfs.c | 21
drivers/gpu/drm/
seq_file.h does not need to be included,so remove it.
Signed-off-by: Yangtao Li
---
drivers/staging/android/ion/ion.c | 1 -
drivers/staging/android/ion/ion_system_heap.c | 1 -
2 files changed, 2 deletions(-)
diff --git a/drivers/staging/android/ion/ion.c
b/drivers/staging/android
On 2018-11-30 3:28 p.m., Dan Williams wrote:
> On Fri, Nov 30, 2018 at 2:19 PM Logan Gunthorpe wrote:
>>
>> Hey,
>>
>> On 2018-11-29 11:51 a.m., Dan Williams wrote:
>>> Got it, let me see how bad moving arch_remove_memory() turns out,
>>> sounds like a decent approach to coordinate multiple user
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/dma-buf/dma-buf.c| 12 +---
drivers/dma-buf/sync_debug.c | 16 +++-
2 files changed, 4 insertions(+), 24 deletions(-)
diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-
On Sun, Dec 2, 2018 at 12:14 PM Yangtao Li wrote:
>
> Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
>
> Signed-off-by: Yangtao Li
> ---
Changes in v2:
-Add a missing edit of dss_fops
---
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
On Fri, Nov 30, 2018 at 5:30 PM Jarkko Sakkinen
wrote:
>
> In order to comply with the CoC, replace with a hug.
>
> Signed-off-by: Jarkko Sakkinen
> ---
> drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c| 2 +-
> drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/macros.fuc | 2 +-
> 2 file
Convert to use vm_insert_range() to map range of kernel
memory to user vma.
Signed-off-by: Souptick Joarder
Tested-by: Heiko Stuebner
Acked-by: Heiko Stuebner
---
drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 20 ++--
1 file changed, 2 insertions(+), 18 deletions(-)
diff --git
On Thu, Nov 29, 2018 at 7:14 PM Luis Chamberlain wrote:
>
> On Wed, Nov 28, 2018 at 11:36:18AM -0800, Brendan Higgins wrote:
> > +#define module_test(module) \
> > + static int module_kunit_init##module(void) \
> > + { \
> > + return kunit_run_tests(&mod
Hi,
I am looking for a way to export the color encoding and range selection
to user space. I came across those properties and am wondering, why
they are meant only for non RGB color encodings. Would it be okay, to
modify them and use with RGB formats as well?
Regards,
Chris
On 02/19/2018 09:28
On Sun, Dec 02, 2018 at 11:49:44AM +0530, Souptick Joarder wrote:
> Previouly drivers have their own way of mapping range of
> kernel pages/memory into user vma and this was done by
> invoking vm_insert_page() within a loop.
>
> As this pattern is common across different drivers, it can
> be gener
Hey,
On 2018-11-29 11:51 a.m., Dan Williams wrote:
> Got it, let me see how bad moving arch_remove_memory() turns out,
> sounds like a decent approach to coordinate multiple users of a single
> ref.
I've put together a patch set[1] that fixes all the users of
devm_memremap_pages() without moving
On Thu, Nov 29, 2018 at 7:28 PM Luis Chamberlain wrote:
>
> > +static void kunit_run_case_internal(struct kunit *test,
> > + struct kunit_module *module,
> > + struct kunit_case *test_case)
> > +{
> > + int ret;
> > +
> > + if
Convert to use vm_insert_range() to map range of kernel
memory to user vma.
Signed-off-by: Souptick Joarder
Reviewed-by: Matthew Wilcox
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/xen/xen_drm_front_gem.c | 20 ++--
1 file changed, 6 insertions(+), 14 deletions(-)
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/video/fbdev/omap2/omapfb/dss/core.c | 18 --
1 file changed, 4 insertions(+), 14 deletions(-)
diff --git a/drivers/video/fbdev/omap2/omapfb/dss/core.c
b/drivers/video/fbdev/omap2/omapfb/
On 30/11/2018 07:43, Stephen Boyd wrote:
> Quoting Matthias Brugger (2018-11-21 09:09:52)
>>
>>
>> On 21/11/2018 17:46, Stephen Boyd wrote:
>>> Quoting Rob Herring (2018-11-19 11:15:16)
On Sun, Nov 18, 2018 at 11:12 AM Matthias Brugger
wrote:
> On 11/17/18 12:15 AM, Rob Herring wro
With GCC version 5 and 6, this uninitialized warning can be seen.
GCC have been fixed in newer versions.
drivers/gpu/drm/sun4i/sun4i_tcon.c: In function ‘sun4i_tcon_bind’:
drivers/gpu/drm/sun4i/sun4i_tcon.c:1091:21: warning: ‘has_lvds_alt’ may be used
uninitialized in this function [-Wmaybe-unini
On Fri, Nov 30, 2018 at 08:13:04AM -0600, Rob Herring wrote:
> > > It's quite unusual for a backlight device to have a trivial binding.
> > >
> > > The driver supports fairly extensive parametrization via struct
> > > lm3530a_platform_data. It is really the case that none of these
> > > properties
https://bugzilla.kernel.org/show_bug.cgi?id=201847
Bug ID: 201847
Summary: nouveau :01:00.0: fifo: fault 01 [WRITE] at
0a721000 engine 00 [GR] client 0f
[GPC0/PROP_0] reason 82 [] on channel 4 [00ff85c000
https://bugs.freedesktop.org/show_bug.cgi?id=95177
Simon changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=95017
--- Comment #19 from Simon ---
*** Bug 95177 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-dev
https://bugs.freedesktop.org/show_bug.cgi?id=95017
Simon changed:
What|Removed |Added
CC||s...@gmx.de
--- Comment #20 from Simon ---
Crea
https://bugs.freedesktop.org/show_bug.cgi?id=95017
Simon changed:
What|Removed |Added
Hardware|PowerPC |All
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=95017
--- Comment #21 from Simon ---
nothing seems to help, I tried agpmode=-1, disabling glamor that didnt help and
Option "NoAccel" "true" wont let me login on the grafical user interface at
all.
--
You are receiving this mail because:
You are the
On Sat, Dec 1, 2018 at 3:47 AM Rob Clark wrote:
>
> On Fri, Nov 30, 2018 at 9:05 PM Tomasz Figa wrote:
> >
> > On Thu, Nov 29, 2018 at 4:23 PM Tomasz Figa wrote:
> > >
> > > On Thu, Nov 29, 2018 at 12:03 PM Robin Murphy
> > > wrote:
> > > >
> > > > On 29/11/2018 19:57, Tomasz Figa wrote:
> > >
On Sat, Dec 1, 2018 at 8:54 AM Rob Clark wrote:
>
> This solves a problem we see with drm/msm, caused by getting
> iommu_dma_ops while we attach our own domain and manage it directly at
> the iommu API level:
>
> [0038] user address but active_mm is swapper
> Internal error: Oops:
https://bugs.freedesktop.org/show_bug.cgi?id=108920
--- Comment #2 from Alex Deucher ---
Created attachment 142693
--> https://bugs.freedesktop.org/attachment.cgi?id=142693&action=edit
possible fix
This patch should fix it.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=108917
--- Comment #2 from Alex Deucher ---
Possibly the same issue as bug 106175.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedes
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #33 from Alex Deucher ---
(In reply to alex.vl from comment #31)
> Comment on attachment 142687 [details] [review]
> Patch to workaround FATAL issue on VCE2.0 ringtest initialization .
>
> Note: Its just workaround .
>
> I see 2 pr
https://bugs.freedesktop.org/show_bug.cgi?id=108704
--- Comment #11 from Alex Deucher ---
(In reply to Laurent Pointecouteau from comment #10)
> (In reply to Alex Deucher from comment #9)
> > Please try the patch in comment 1.
>
> I've applied the patch and there are no more amdgpu related error
Hi, Nicolas:
On Mon, 2018-11-26 at 13:30 +0800, CK Hu wrote:
> Hi, Nicolas:
>
> On Mon, 2018-11-26 at 12:07 +0800, Nicolas Boichat wrote:
> > Even if dsi->bridge is NULL, we still try to call drm_bridge_attach,
> > and print out an error message, before creating the connector.
> >
> > When no br
https://bugzilla.kernel.org/show_bug.cgi?id=198669
Dave Airlie (airl...@linux.ie) changed:
What|Removed |Added
CC||airl...@linux.ie
--- Com
On 2018年11月28日 22:50, Christian König wrote:
Lockless container implementation similar to a dma_fence_array, but with
only two elements per node and automatic garbage collection.
v2: properly document dma_fence_chain_for_each, add dma_fence_chain_find_seqno,
drop prev reference during gar
Hey Matt,
On Fri, Nov 30, 2018 at 5:22 PM Matt Roper wrote:
> I think Joonas is describing something closer in
> design to the cgroup-v2 "cpu" controller, which partitions the general
> time/usage allocated to via cgroup; afaiu, "cpu" doesn't really care
> which specific core the tasks run on, ju
On Fri, 30 Nov 2018, Enric Balletbo Serra wrote:
> Hi,
> Missatge de Enric Balletbo i Serra del
> dia dc., 7 de nov. 2018 a les 9:56:
> >
> > Commit '88ba95bedb79 ("backlight: pwm_bl: Compute brightness of LED
> > linearly to human eye")' allows the possibility to compute a default
> > brightness
https://bugs.freedesktop.org/show_bug.cgi?id=107793
--- Comment #11 from Simon Geard ---
Is there any update on this, any more information I can provide to help get
this fixed? I can confirm it's still occurring on the 4.19.5-200 kernel
currently included in Fedora 28...
--
You are receiving th
68 matches
Mail list logo
