https://bugzilla.kernel.org/show_bug.cgi?id=196125
--- Comment #3 from cont...@florentflament.com ---
I just figured out that the flickering occurs only when logging using Wayland.
When using xorg, there is no flickering (I attached xorg log files in case it
may be useful). I'll attach Wayland log
https://bugzilla.kernel.org/show_bug.cgi?id=196125
--- Comment #4 from cont...@florentflament.com ---
Created attachment 257081
--> https://bugzilla.kernel.org/attachment.cgi?id=257081&action=edit
Xorg log file
Please note that the flickering doesn't occur when using xorg.
This file is just the
https://bugs.freedesktop.org/show_bug.cgi?id=101512
Bug ID: 101512
Summary: Crash on Enlightenment with forked child
Product: Mesa
Version: 17.1
Hardware: Other
OS: All
Status: NEW
Severity: normal
On Mon, Jun 19, 2017 at 6:34 PM, Al Viro wrote:
> On Mon, Jun 19, 2017 at 10:15:09AM -0600, Jordan Crouse wrote:
>
>> Which raised a bikeshed debate over whether it is appropriate to mark a
>> scalar
>> type as __user. My opinion is that it is appropriate because __user should
>> mark
>> user m
On 20.06.2017 08:56, Archit Taneja wrote:
>
> On 06/19/2017 03:42 PM, Boris Brezillon wrote:
>> On Tue, 13 Jun 2017 11:02:47 +0200
>> Andrzej Hajda wrote:
>>
>>> Hi,
>>>
>>> Just spotted this thread.
>>>
>>> On 06.06.2017 14:58, Tomi Valkeinen wrote:
On 06/06/17 15:48, Boris Brezillon wrote:
https://bugs.freedesktop.org/show_bug.cgi?id=101499
--- Comment #9 from Michel Dänzer ---
(In reply to Carlo Caione from comment #8)
> On a side note: is it normal so many error messages in the journal? Like:
>
> kernel: amdgpu :00:01.0: 9cccade4d800 pin failed
> kernel: [drm:amdgpu_crtc
Hi Archit,
On Tuesday 20 Jun 2017 09:18:00 Archit Taneja wrote:
> On 06/16/2017 08:13 PM, Eric Anholt wrote:
> > Archit Taneja writes:
> >> On 06/16/2017 02:11 AM, Eric Anholt wrote:
> >>> If the panel-bridge is being set up after the drm_mode_config_reset(),
> >>> then the connector's state woul
Hi,
> Yep that's cargo-culted, but from a quick grep only msm and qxl
> headers do this (the other __user annotations in uapi/drm are for
> pointers, where it's correct). Adding those maintainers.
Yep, those looks pointless indeed.
> Also, if you use u64_to_user_ptr helper macro sparse should
Hi Dave,
On Tue, Jun 20, 2017 at 11:17:13AM +1000, Dave Airlie wrote:
> On 20 June 2017 at 00:56, Liviu Dudau wrote:
> > Hi Dave,
> >
> > Couple of fixes for HDLCD driver to fix an error message when
> > working with TDA19988 driver and moving the framebuffer's physical
> > address calculation to
On Thu, Jun 15, 2017 at 02:58:15PM +0200, Thierry Reding wrote:
> On Wed, May 24, 2017 at 04:51:45PM +0200, Daniel Vetter wrote:
> [...]
> > -Resources allocated by :c:func:`drm_vblank_init()` must be freed
> > -with a call to :c:func:`drm_vblank_cleanup()` in the driver unload
> > -operation handl
On Thu, Jun 01, 2017 at 03:37:33PM +, Vincent ABRIOU wrote:
>
>
> On 05/24/2017 04:52 PM, Daniel Vetter wrote:
> > Seems entirely cargo-culted.
> >
> > Cc: Benjamin Gaignard
> > Cc: Vincent Abriou
> > Signed-off-by: Daniel Vetter
> > ---
> > drivers/gpu/drm/sti/sti_drv.c | 1 -
> > 1 f
On Thu, Jun 15, 2017 at 03:00:08PM +0200, Thierry Reding wrote:
> On Wed, May 24, 2017 at 04:52:08PM +0200, Daniel Vetter wrote:
> > Again, doesn't seem to serve a purpose.
> >
> > Cc: Thierry Reding
> > Signed-off-by: Daniel Vetter
> > ---
> > drivers/gpu/drm/tegra/drm.c | 5 +
> > 1 file
https://bugs.freedesktop.org/show_bug.cgi?id=101512
Christian König changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Tue, Jun 20, 2017 at 10:15 AM, Liviu Dudau wrote:
>
> On Tue, Jun 20, 2017 at 11:17:13AM +1000, Dave Airlie wrote:
>> On 20 June 2017 at 00:56, Liviu Dudau wrote:
>> > Hi Dave,
>> >
>> > Couple of fixes for HDLCD driver to fix an error message when
>> > working with TDA19988 driver and moving
https://bugs.freedesktop.org/show_bug.cgi?id=101512
--- Comment #2 from Apostolos B. ---
According to the E devs.
"it's not calling any gl from the forked child. it's your own atexit() handlers
doing gl stuff in the forked child just when it calls exit. the app does not
expect or try to make gl
On Tue, Jun 20, 2017 at 9:42 AM, Gerd Hoffmann wrote:
>> Yep that's cargo-culted, but from a quick grep only msm and qxl
>> headers do this (the other __user annotations in uapi/drm are for
>> pointers, where it's correct). Adding those maintainers.
>
> Yep, those looks pointless indeed.
>
>> Also
On Fri, Jun 02, 2017 at 01:10:00PM -0700, Eric Anholt wrote:
> Jose Abreu writes:
>
> > Now that we have a callback to check if crtc and encoder supports a
> > given mode we can use it in vc4 so that we restrict the number of
> > probbed modes to the ones we can actually display.
>
> "probed"
>
On Wed, Jun 07, 2017 at 01:07:33AM +, Brown, Aaron F wrote:
> > From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On Behalf
> > Of Jeff Kirsher
> > Sent: Tuesday, June 6, 2017 1:46 PM
> > To: David Miller ; Nikula, Jani
> >
> > Cc: Ursulin, Tvrtko ; daniel.vet...@ffwll.ch;
> >
On Thu, Jun 01, 2017 at 01:59:34PM +0200, Hans de Goede wrote:
> Grain-media GM12U320 based devices are mini video projectors using USB for
> both power and video data transport.
>
> This commit adds a kms driver for these devices, including prime support.
>
> This driver is based on the existing
On Thu, Jun 01, 2017 at 07:25:46PM +0100, Emil Velikov wrote:
> On 1 June 2017 at 14:00, Chris Wilson wrote:
> > Daniel started a crusade a few years back to move control over the
> > initialisation and teardown into the driver rather than drm core, for
> > greater control and far fewer surprises.
On Mon, Jun 05, 2017 at 02:56:04PM -0700, Puthikorn Voravootivat wrote:
> This patch set contain 3 patches which are already reviewed by DK.
> Another 6 patches in previous version was already merged in v7 and v9.
> - First patch sets the PWM freqency to match data in panel vbt.
> - Next patch adds
On Tue, Jun 06, 2017 at 09:17:06AM +0200, Lucas Stach wrote:
> GPU buffers can be quite large, so userspace is expected to deal with
> allocation failure. Don't trigger the OOM killer when page allocation for
> the GEM objects fails, as this opens an easy possiblity for unprivileged
> applications
https://bugs.freedesktop.org/show_bug.cgi?id=101499
--- Comment #10 from Carlo Caione ---
> I think all of these are triggered by VRAM being too small to fit the
> scanout buffers covering the laptop panel + external monitor.
Probably I'm missing something, but when the HDMI is connected everythi
On Tue, Jun 06, 2017 at 12:26:57PM +0300, Jani Nikula wrote:
> On Sun, 04 Jun 2017, "H.J. Lu" wrote:
> > Please CC me since I am not on this mailing list.
>
> Sorry, should've instructed you to send to dri-devel instead of
> intel-gfx, because the patch touches drm helpers. Cc'd.
>
> BR,
> Jani.
On Tue, Jun 20, 2017 at 10:34:05AM +0200, Daniel Vetter wrote:
> On Tue, Jun 20, 2017 at 10:15 AM, Liviu Dudau wrote:
> >
> > On Tue, Jun 20, 2017 at 11:17:13AM +1000, Dave Airlie wrote:
> >> On 20 June 2017 at 00:56, Liviu Dudau wrote:
> >> > Hi Dave,
> >> >
> >> > Couple of fixes for HDLCD driv
In
commit 91eefc05f0ac71902906b2058360e61bd25137fe
Author: Daniel Vetter
Date: Wed Dec 14 00:08:10 2016 +0100
drm: Tighten locking in drm_mode_getconnector
I reordered the logic a bit in that IOCTL, but that broke userspace
since it'll get the new mode list, but not the new property value
On Thu, Jun 08, 2017 at 03:25:25PM +0200, Christoph Hellwig wrote:
> Hi all,
>
> for a while we have a generic implementation of the dma mapping routines
> that call into per-arch or per-device operations. But right now there
> still are various bits in the interfaces where don't clearly operate
On Tue, Jun 13, 2017 at 10:23:34AM +0100, Emil Velikov wrote:
> Hi Daniel,
>
> On 9 June 2017 at 07:57, Daniel Axtens wrote:
> > Currently, calling drmGetBusid from libdrm on a hibmc VGA
> > card returns a string like "0007:a1:00.0".
> >
> > The busid reported by most cards begins with "pci:". Fo
Am Dienstag, den 20.06.2017, 11:06 +0200 schrieb Daniel Vetter:
> On Tue, Jun 06, 2017 at 09:17:06AM +0200, Lucas Stach wrote:
> > GPU buffers can be quite large, so userspace is expected to deal with
> > allocation failure. Don't trigger the OOM killer when page allocation for
> > the GEM objects
https://bugs.freedesktop.org/show_bug.cgi?id=101499
--- Comment #11 from Michel Dänzer ---
(In reply to Carlo Caione from comment #10)
> Probably I'm missing something, but when the HDMI is connected everything
> works fine, with the scanout buffer correctly displayed on the laptop panel
> + exte
Hi Dave,
Updated the tree to drop any additional commits and tagged the top
commit.
> Couple of fixes for HDLCD driver to fix an error message when
> working with TDA19988 driver and moving the framebuffer's physical
> address calculation to use the DRM CMA helper.
Best regards,
Liviu
The foll
On Tue, Jun 20, 2017 at 11:22:06AM +0200, Lucas Stach wrote:
> Am Dienstag, den 20.06.2017, 11:06 +0200 schrieb Daniel Vetter:
> > On Tue, Jun 06, 2017 at 09:17:06AM +0200, Lucas Stach wrote:
> > > GPU buffers can be quite large, so userspace is expected to deal with
> > > allocation failure. Don't
On Tue, 20 Jun 2017, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in that IOCTL, but that broke userspace
> since
On Mon, Jun 19, 2017 at 04:11:35PM -0400, Andrey Grodzovsky wrote:
>
>
> On 06/19/2017 03:24 PM, Sean Paul wrote:
> > On Mon, Jun 19, 2017 at 11:35:28AM -0400, Harry Wentland wrote:
> > > On 2017-06-09 05:30 PM, Andrey Grodzovsky wrote:
> > > > Problem:
> > > > While running IGT kms_atomic_transi
On Thu, Jun 15, 2017 at 12:15:58PM +0200, Boris Brezillon wrote:
> On Thu, 15 Jun 2017 11:54:29 +0200
> Peter Rosin wrote:
>
> > On 2017-06-13 17:30, Boris Brezillon wrote:
> > > Hi Peter,
> > >
> > > On Tue, 13 Jun 2017 16:34:25 +0200
> > > Peter Rosin wrote:
> > >
> > >> Hi!
> > >>
> > >>
On Mon, Jun 19, 2017 at 05:45:21PM +0200, Noralf Trønnes wrote:
>
> Den 19.06.2017 15.17, skrev Liviu Dudau:
> > On Fri, Jun 16, 2017 at 06:58:36PM +0200, Noralf Trønnes wrote:
> > > Den 16.06.2017 15.53, skrev Liviu Dudau:
> > > > Update the PM code to suspend/resume the fbdev_cma console.
> > >
On Sat, Jun 17, 2017 at 07:48:04PM +0200, Peter Rosin wrote:
> The clut is not synchronized with the drm gamma_lut state.
>
> Signed-off-by: Peter Rosin
This needs to be done in the fbdev helper, not like this. Yes it's an old
issue, but forcing every driver to duplicate code like this isn't coo
On Sat, Jun 17, 2017 at 07:48:02PM +0200, Peter Rosin wrote:
> All layers of all supported chips support this, the only variable is the
> base address of the lookup table in the register map.
>
> Signed-off-by: Peter Rosin
As Boris said, pls use the new color manager stuff for atomic drivers, an
It's not obvious that when using the new color manager stuff you still
need to wire up the legacy helper to get legacy LUT support. Improve
this with more links. drm_crtc_funcs->gamma_set already explains this
properly.
Cc: Peter Rosin
Cc: Boris Brezillon
Signed-off-by: Daniel Vetter
---
drive
https://bugs.freedesktop.org/show_bug.cgi?id=101499
--- Comment #12 from Carlo Caione ---
Created attachment 132081
--> https://bugs.freedesktop.org/attachment.cgi?id=132081&action=edit
Corruption using xf86-video-amdgpu HEAD
Interesting. Thank you for explaining this and your time.
I just tr
On Tue, 20 Jun 2017 11:42:28 +0200
Daniel Vetter wrote:
> It's not obvious that when using the new color manager stuff you still
> need to wire up the legacy helper to get legacy LUT support. Improve
> this with more links. drm_crtc_funcs->gamma_set already explains this
> properly.
>
> Cc: Pete
I'm not 100% sure what this is all about, but it clearly won't work like
this.
diff --git a/include/drm/amdgpu_drm.h b/include/drm/amdgpu_drm.h
index df250de..dcbe22c 100644
--- a/include/drm/amdgpu_drm.h
+++ b/include/drm/amdgpu_drm.h
@@ -832,7 +832,7 @@ struct drm_amdgpu_info_device {
On 19 June 2017 at 17:31, Krzysztof Kozlowski wrote:
> Although header is included only once but still having an include guard
> is a good practice. To avoid confusion, add SoC prefix to existing
> Exynos5433 header include guard.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> include/video/exy
https://bugs.freedesktop.org/show_bug.cgi?id=101382
cosiek...@o2.pl changed:
What|Removed |Added
Summary|[r300] Electronic super joy |[r300] Electronic super joy
https://bugs.freedesktop.org/show_bug.cgi?id=93826
--- Comment #72 from i...@posteo.net ---
Created attachment 132082
--> https://bugs.freedesktop.org/attachment.cgi?id=132082&action=edit
parsed EDID from different MG279q
Thanks for that. The new EDID shows in fact other modes and timings, atta
On Tue, Jun 20, 2017 at 11:48:05AM +0200, Boris Brezillon wrote:
> On Tue, 20 Jun 2017 11:42:28 +0200
> Daniel Vetter wrote:
>
> > It's not obvious that when using the new color manager stuff you still
> > need to wire up the legacy helper to get legacy LUT support. Improve
> > this with more lin
On Tue, Jun 20, 2017 at 11:49:23AM +0200, Christian König wrote:
> I'm not 100% sure what this is all about, but it clearly won't work like
> this.
>
> > diff --git a/include/drm/amdgpu_drm.h b/include/drm/amdgpu_drm.h
> > index df250de..dcbe22c 100644
> > --- a/include/drm/amdgpu_drm.h
> > +++ b/
drm_fbdev_cma_set_suspend{,_unlocked} use an integer parameter
to describe whether the intended state is a suspend or a resume.
It then passes the value to drm_fb_helper_set_suspend{,_unlocked}
which uses a boolean. Switch to using bool everywhere.
Signed-off-by: Liviu Dudau
---
drivers/gpu/drm/
On 20 June 2017 at 11:02, Krzysztof Kozlowski wrote:
> On Tue, Jun 20, 2017 at 11:53 AM, Emil Velikov
> wrote:
>> On 19 June 2017 at 17:31, Krzysztof Kozlowski wrote:
>>> Although header is included only once but still having an include guard
>>> is a good practice. To avoid confusion, add SoC
2017-06-20 7:05 GMT+02:00 Arvind Yadav :
> of_device_ids are not supposed to change at runtime. All functions
> working with of_device_ids provided by work with const
> of_device_ids. So mark the non-const structs as const.
>
> File size before:
>textdata bss dec hex filename
>
2017-06-20 6:55 GMT+02:00 Arvind Yadav :
> Replace '%d' by '%zu' and '%lu' to fix the following compilation warning:-
>
> drivers/gpu/drm/sti/sti_hqvdp.c: In function ‘sti_hqvdp_start_xp70’:
> drivers/gpu/drm/sti/sti_hqvdp.c:925:3: warning: format ‘%d’ expects argument
> of type ‘int’, but argumen
Fix qxl __user annotations in uapi include.
Also some more sparse easy warnings.
Some iomem address space issues left for another day.
Gerd Hoffmann (3):
drm/qxl: fix __user annotations
drm/qxl: declare a bunch of functions as static
drm/qxl: move extern variable declaration header file
dr
Drop them from u64 fields, tag local variables correctly instead.
While being at it switch the code to use u64_to_user_ptr().
Signed-off-by: Gerd Hoffmann
Acked-by: Daniel Vetter
---
include/uapi/drm/qxl_drm.h | 6 +++---
drivers/gpu/drm/qxl/qxl_ioctl.c | 17 +
2 files cha
Flagged by sparse.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_display.c | 18 +-
drivers/gpu/drm/qxl/qxl_object.c | 4 ++--
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_display.c
b/drivers/gpu/drm/qxl/qxl_display.c
inde
Flagged by sparse.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_drv.h | 1 +
drivers/gpu/drm/qxl/qxl_drv.c | 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/qxl/qxl_drv.h b/drivers/gpu/drm/qxl/qxl_drv.h
index 3591d2330a..3397a19073 100644
--- a/drive
Hi Arvind,
[auto build test WARNING on drm/drm-next]
[also build test WARNING on v4.12-rc6 next-20170620]
[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/commits/Arvind-Yadav/drm-sti-sti_hqvdp-Fix
Change-Id: Ie2a812716a6802f7a5a0bc09b1a8db824c5bf2ed
Signed-off-by: Flora Cui
---
amdgpu/amdgpu.h | 2 +-
amdgpu/amdgpu_gpu_info.c | 2 +-
include/drm/amdgpu_drm.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/amdgpu/amdgpu.h b/amdgpu/amdgpu.h
index b6779f9..34ca
On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote:
> I plan to create a new dma-mapping tree to collect all this work.
> Any volunteers for co-maintainers, especially from the iommu gang?
Ok, I've created the new tree:
git://git.infradead.org/users/hch/dma-mapping.git for-next
Hi Dave,
drm-intel-next-2017-06-19:
Final pile of features for 4.13
New uabi:
- batch bo in first slot, for faster execbuf assembly in userspace
(Chris Wilson)
- (sub)slice getparam, needed for mesa perf support (Robert Bragg)
First pile of patches for cnl/cfl support, maintained by Rodrigo bu
Hi Christoph,
On Tue, 20 Jun 2017 14:41:40 +0200 Christoph Hellwig wrote:
>
> On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote:
> > I plan to create a new dma-mapping tree to collect all this work.
> > Any volunteers for co-maintainers, especially from the iommu gang?
>
> Ok,
Hi Christoph,
On 20/06/17 13:41, Christoph Hellwig wrote:
> On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote:
>> I plan to create a new dma-mapping tree to collect all this work.
>> Any volunteers for co-maintainers, especially from the iommu gang?
>
> Ok, I've created the new tr
On Tue, Jun 20, 2017 at 02:14:36PM +0100, Robin Murphy wrote:
> Hi Christoph,
>
> On 20/06/17 13:41, Christoph Hellwig wrote:
> > On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote:
> >> I plan to create a new dma-mapping tree to collect all this work.
> >> Any volunteers for co-mai
On Tue, Jun 20, 2017 at 11:04:00PM +1000, Stephen Rothwell wrote:
> git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git#dma-mapping-next
>
> Contacts: Marek Szyprowski and Kyungmin Park (cc'd)
>
> I have called your tree dma-mapping-hch for now. The other tree has
> not been updated si
On Tue, Jun 20, 2017 at 11:19:02AM +0200, Daniel Vetter wrote:
> Ack for the 2 drm patches, but I can also pick them up through drm-misc if
> you prefer that (but then it'll be 4.14).
Nah, I'll plan to set up a dma-mapping tree so that we'll have common
place for dma-mapping work.
On Tue, Jun 20, 2017 at 06:38:00PM +0530, Bhumika Goyal wrote:
> Add const to drm_encoder_helper_funcs structures as they are only passed
> as an argument to the function drm_encoder_helper_add and this argument
> is of type const. So, add const to these structures.
>
> Signed-off-by: Bhumika Goya
On Mon, 2017-06-19 at 21:38 +0530, Shashank Sharma wrote:
> This patch checks encoder level support for HDMI YCBCR outputs.
> HDMI output mode is a connector property, this patch checks if
> source and sink can support the HDMI output type selected by user.
> And if they both can, it commits the hd
On Tue, Jun 20, 2017 at 11:23:20AM +0100, Liviu Dudau wrote:
> drm_fbdev_cma_set_suspend{,_unlocked} use an integer parameter
> to describe whether the intended state is a suspend or a resume.
> It then passes the value to drm_fb_helper_set_suspend{,_unlocked}
> which uses a boolean. Switch to usin
Hi Jose,
Am Freitag, 9. Juni 2017, 13:53:12 CEST schrieb Jose Abreu:
> On 09-06-2017 12:04, Jose Abreu wrote:
> > Currently HDMI 2.0 PHYs do not have a default configuration function.
> >
> > As these PHYs have the same register layout as the 3D PHYs we can
> > safely use the default configuratio
On Tue, Jun 20, 2017 at 01:39:13PM +0200, Gerd Hoffmann wrote:
> Fix qxl __user annotations in uapi include.
> Also some more sparse easy warnings.
> Some iomem address space issues left for another day.
>
> Gerd Hoffmann (3):
> drm/qxl: fix __user annotations
> drm/qxl: declare a bunch of fun
Hi Dave,
One more -misc-next pull for 4.13 from drm-misc-next. These 3 patches came less
than an hour after my last PR, so we'll sneak these in and cut over to
next-fixes after this.
All 3 are vc4. 2 add tiling support to vc4 and the other replaces hand-rolled
atomic commit code with the helpers.
Hi Dave, a mixed bag of i915 fixes. The memory allocation changes from
Chris and deadlock fixes from Ville are the important ones.
BR,
Jani.
The following changes since commit c380f681245d7ae57f17d9ebbbe8f8f1557ee1fb:
drm/i915: Fix GVT-g PVINFO version compatibility check (2017-06-13 11:19:22
Hi Rob,
On Wed, Jun 14, 2017 at 2:49 PM, Thierry Reding
wrote:
> On Tue, Apr 25, 2017 at 01:18:35PM -0300, Marco Franchi wrote:
>> Add driver for Seiko Instruments Inc. 4.3" WVGA (800 x RGB x 480)
>> TFT with Touch-Panel.
>>
>> Datasheet available at:
>> http://www.glyn.de/data/glyn/media/doc/43w
https://bugs.freedesktop.org/show_bug.cgi?id=101499
--- Comment #13 from Carlo Caione ---
> I just tried the HEAD of xf86-video-amdgpu and now instead of
> having a black screen I have the image corruption as shown
> in the picture.
Just FYI this is due to commit b09fde0d81 ("Use reference counti
Hey,
This was reported back in February and it seems nobody's given a shit?
I've got a machine here with a Quadro 4000 that the screen locks up on
every single time the monitor goes to sleep. Userspace is Ubuntu 16.04,
kernel is recent mainline (4.12-rc4+). It's been happening since 4.10
though.
Hi Dave,
A few fixes for 4.12:
- Add a new Polaris12 pci id
- A stack corruption fix
- Suspend/resume fix
- PX fix
- Display flickering fix
The following changes since commit 7119dbdf7c52042acb1b02f116fa3257e97659ea:
Merge tag 'drm-intel-fixes-2017-06-15' of
git://anongit.freedesktop.org/git/
On Tue, Jun 20, 2017 at 12:54 PM, Olof Johansson wrote:
> Hey,
>
> This was reported back in February and it seems nobody's given a shit?
>
Apparently not -- including you. Someone who was interested in seeing this
issue fixed would certainly have provided a kernel bisection result as it's
appar
Archit Taneja writes:
> On 06/16/2017 08:13 PM, Eric Anholt wrote:
>> Archit Taneja writes:
>>
>>> On 06/16/2017 02:11 AM, Eric Anholt wrote:
If the panel-bridge is being set up after the drm_mode_config_reset(),
then the connector's state would never get initialized, and we'd
de
On Tue, 2017-06-20 at 11:03 +0200, Daniel Vetter wrote:
> On Mon, Jun 05, 2017 at 02:56:04PM -0700, Puthikorn Voravootivat wrote:
> > This patch set contain 3 patches which are already reviewed by DK.
> > Another 6 patches in previous version was already merged in v7 and v9.
> > - First patch se
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #20 from Carlo Caione ---
> That could be a plymouth bug. I've noticed that it doesn't seem to call
> drmModeCrtcSetGamma to make sure the display CLUTs are initialized to
> appropriate values.
Can you expand on this a little bit?
I
https://bugs.freedesktop.org/show_bug.cgi?id=101294
Marek Olšák changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
Problem : While running IGT kms_atomic_transition test suite i encountered
a hang in drmHandleEvent immediately following an atomic_commit.
After dumping the atomic state I relized that in this case there was
not even one CRTC attached to the state and only disabled
planes. This probably due to a
https://bugs.freedesktop.org/show_bug.cgi?id=100070
--- Comment #9 from Marek Olšák ---
It might be a WQM vs KILL issue.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.or
On Tue, Jun 20, 2017 at 11:16 AM, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in that IOCTL, but that broke user
https://bugs.freedesktop.org/show_bug.cgi?id=101528
Bug ID: 101528
Summary: RX460 Memory clock stays high until card is "used"
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Hi Dave,
This time around, the biggest thing is a bunch of GEM rework for more
fine grained locking and prep work to handle multiple address spaces
(ie. per-process pagetables). Also some HDMI fixes for 8x96
(snapdragon 820).
One unrelated bus patch, for something that seems to get merged
throug
https://bugs.freedesktop.org/show_bug.cgi?id=100070
--- Comment #10 from Marek Olšák ---
I have a basic initial fix for the grass issue. It works as follows.
The GLSL discard call site sets a flag that the pixel should be killed, but
doesn't kill the thread. The thread is killed at the end of th
On Tue, 2017-06-20 at 11:16 +0200, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in that IOCTL, but that brok
In zap_shader_load_mdt(), we pass a pointer to a phys_addr_t
into dmam_alloc_coherent, which the compiler warns about:
drivers/gpu/drm/msm/adreno/a5xx_gpu.c: In function 'zap_shader_load_mdt':
drivers/gpu/drm/msm/adreno/a5xx_gpu.c:54:50: error: passing argument 3 of
'dmam_alloc_coherent' from inc
When compile-testing for something other than ARCH_QCOM,
we run into a link error:
drivers/gpu/drm/msm/adreno/a5xx_gpu.o: In function `a5xx_hw_init':
a5xx_gpu.c:(.text.a5xx_hw_init+0x600): undefined reference to
`qcom_mdt_get_size'
a5xx_gpu.c:(.text.a5xx_hw_init+0x93c): undefined reference to `qc
In
commit 91eefc05f0ac71902906b2058360e61bd25137fe
Author: Daniel Vetter
Date: Wed Dec 14 00:08:10 2016 +0100
drm: Tighten locking in drm_mode_getconnector
I reordered the logic a bit in that IOCTL, but that broke userspace
since it'll get the new mode list, but not the new property value
On Tue, Jun 20, 2017 at 9:32 PM, Pandiyan, Dhinakaran
wrote:
> Isn't this overwriting the -EFAULT return in case copy_to_user() failed
> while copying the modes ?
Indeed, thanks for spotting this. New patch in-flight.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 5
The last rework left behind two unused variables:
drm/arm/hdlcd_crtc.c: In function 'hdlcd_plane_atomic_update':
drm/arm/hdlcd_crtc.c:264:13: warning: unused variable 'src_y'
[-Wunused-variable]
drm/arm/hdlcd_crtc.c:264:6: warning: unused variable 'src_x' [-Wunused-variable]
This removes them.
On 06/21/2017 02:54 AM, Olof Johansson wrote:
> Hey,
>
> This was reported back in February and it seems nobody's given a shit?
>
> I've got a machine here with a Quadro 4000 that the screen locks up on
> every single time the monitor goes to sleep. Userspace is Ubuntu 16.04,
> kernel is recent m
On Tue, Jun 20, 2017 at 10:28:37PM +0200, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in that IOCTL, but that
On Tue, 2017-06-20 at 22:28 +0200, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in that IOCTL, but that brok
https://bugs.freedesktop.org/show_bug.cgi?id=93826
--- Comment #73 from Eike ---
(In reply to iuno from comment #72)
> Another, slightly off-topic, question: the VertRefresh value shows the
> FreeSync range for my display (35-90), your values are 50-144, does that
> mean you can actually use Free
https://bugs.freedesktop.org/show_bug.cgi?id=98795
Samuel Pitoiset changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 2017年06月20日 21:07, Bhumika Goyal wrote:
Add const to drm_encoder_helper_funcs structures as they are only passed
as an argument to the function drm_encoder_helper_add and this argument
is of type const. So, add const to these structures. Also, fix line over
80 characters warning while adding c
Hi!
While trying to get CLUT support for the atmel_hlcdc driver, and
specifically for the emulated fbdev interface, I received some
push-back that my feeble in-driver attempts should be solved
by the core. This is my attempt to do it right.
Boris and Daniel, was this approximately what you had in
Replace '%d' by '%zu' and '%lu' to fix the following compilation warning:-
drivers/gpu/drm/sti/sti_hqvdp.c: In function ‘sti_hqvdp_start_xp70’:
drivers/gpu/drm/sti/sti_hqvdp.c:925:3: warning: format ‘%d’ expects argument of
type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
DRM_ERROR("In
1 - 100 of 143 matches
Mail list logo
