On Fri, Jan 11, 2019 at 11:16:38PM +0100, Daniel Vetter wrote:
> On Fri, Jan 11, 2019 at 11:06:20PM +0100, Daniel Vetter wrote:
> > On Fri, Jan 11, 2019 at 09:02:34AM -0500, Rob Clark wrote:
> > > This fixes an '*ERROR* connector VGA-2 leaked!' splat at driver unload.
> > >
> > > Signed-off-by: Ro
https://bugs.freedesktop.org/show_bug.cgi?id=109345
Bug ID: 109345
Summary: drm-next-2018-12-14 -Linux PPC
Product: DRI
Version: XOrg git
Hardware: PowerPC
OS: Linux (All)
Status: NEW
Severity: normal
On 2019年01月11日 21:15, Christian König wrote:
Move the BO on the LRU only when it is actually moved by a DMA
operation.
Signed-off-by: Christian König
Tested-And-Reviewed-by: Chunming Zhou
I just sent lru_notify v2 patches, please review them. With yours and
mine, the OOM issue is fixed w
allow driver do somethings when lru changed.
v2:
address Michel's comments.
Change-Id: Ie82053da49272881d4b52b1c406f7c221a3fcadf
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/ttm/ttm_bo.c| 11 +++
include/drm/ttm/ttm_bo_driver.h | 9 +
2 files changed, 16 insertions(+), 4
if lru is changed, we cannot do bulk moving.
v2:
root bo isn't bulk moving, skip its change.
Change-Id: Ide0fe920295cc25f7cabcf41a6400519e5783f2a
Signed-off-by: Chunming Zhou
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 3 ++-
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 22 ++
https://bugs.freedesktop.org/show_bug.cgi?id=109265
--- Comment #4 from Timothy Arceri ---
This is odd. As far as I can tell the shader variant produced after loading
from the case is the same as the one produced when the cache is disabled.
Its also a fairly simple program. From tests/texturing/
https://bugs.freedesktop.org/show_bug.cgi?id=109342
Sih Sîng-hông changed:
What|Removed |Added
CC||ihc...@gmail.com
--- Comment #1 from Si
https://bugs.freedesktop.org/show_bug.cgi?id=109342
Bug ID: 109342
Summary: Display is frozen in X, but mouse cursor moves when
using fcitx with nouveau.
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=109234
--- Comment #15 from bmil...@gmail.com ---
@Sibren Vasse
Have you forwarded this to dma devs yet?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dr
Hi Dave,
The following changes since commit e3d093070eb0b5e3df668d3eb04100ea79343c65:
Merge tag 'tilcdc-4.22' of https://github.com/jsarha/linux into drm-next
(2019-01-11 06:29:31 +1000)
are available in the Git repository at:
git://linuxtv.org/pinchartl/media.git tags/du-next-20190114
fo
On 1/13/19 3:19 PM, David Lechner wrote:
On 1/11/19 2:12 PM, Noralf Trønnes wrote:
This switches to drm_atomic_helper_dirtyfb() as the framebuffer dirty
handler. All flushing will now happen in the pipe functions.
Also enable the damage plane property for all except repaper which can
only do fu
On Fri, 2019-01-11 at 17:07 +0100, Noralf Trønnes wrote:
>
> Den 11.01.2019 11.25, skrev Daniel Vetter:
> > On Fri, Jan 11, 2019 at 05:49:15PM +0800, CK Hu wrote:
> >> Hi, Daniel:
> >>
> >> On Fri, 2019-01-11 at 10:20 +0100, Daniel Vetter wrote:
> >>> On Fri, Jan 11, 2019 at 11:20:09AM +0800, CK H
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #41 from Shmerl ---
Same thing still happen with 5.0-rc2. Does anyone else experience this race
condition when the monitor goes to sleep right after boot? It is related to the
same setup (DisplayPort 1.2), since it's not happening wi
https://bugs.freedesktop.org/show_bug.cgi?id=109234
Sibren Vasse changed:
What|Removed |Added
Summary|amdgpu random hangs with|amdgpu random hangs with
https://bugs.freedesktop.org/show_bug.cgi?id=109340
--- Comment #2 from Rafał Miłecki ---
I've noticed that:
1) After connecting monitor to the docking station's DP output following
outputs appear: DisplayPort-3, DisplayPort-4 and DisplayPort-5.
2) After disconnecting monitor from docking statin
https://bugs.freedesktop.org/show_bug.cgi?id=109340
--- Comment #1 from Rafał Miłecki ---
Created attachment 143093
--> https://bugs.freedesktop.org/attachment.cgi?id=143093&action=edit
Detailed logs of all connecting/disconnecting operations
--
You are receiving this mail because:
You are th
https://bugs.freedesktop.org/show_bug.cgi?id=109340
Bug ID: 109340
Summary: HDMI output (DisplayPort-0) stops listing modes after
using docking station DP output
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=109336
--- Comment #1 from Dominik 'Rathann' Mierzejewski ---
Downstream (Fedora) bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1665766 .
--
You are receiving this mail because:
You are the assignee for the bug._
On 1/11/19 2:12 PM, Noralf Trønnes wrote:
This switches to drm_atomic_helper_dirtyfb() as the framebuffer dirty
handler. All flushing will now happen in the pipe functions.
Also enable the damage plane property for all except repaper which can
only do full updates.
ili9225:
This change made ili
Hi Douglas,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robclark/msm-next]
[also build test ERROR on v5.0-rc1 next-20190111]
[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/li
Add maintainers and reviewers for VKMS driver
Signed-off-by: Rodrigo Siqueira
---
Changes in v2:
- Insert the section in alphabetical order
Resend:
- Update patch due to changes in MAINTAINER file
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAI
Hi,
I resend this patch for CI via “intel-...@lists.freedesktop.org” as
Daniel suggested, and I got a feedback that reported an issue as can be
seen here:
https://patchwork.freedesktop.org/series/51147/
After a careful analysis of what happened, I concluded that the problem
is related to the
https://bugs.freedesktop.org/show_bug.cgi?id=109124
--- Comment #3 from Sylvain BERTRAND ---
You can increase significantly the performance issue while taking some height:
climb to the top of the "water station", turn to look anywhere, the fps drops
below 30fps. Seems to be significantly linked t
You can increase significantly the performance issue while taking some height:
climb to the top of the "water station", turn to look anywhere, the fps drops
below 30fps. Seems to be significantly linked to the 3d engine performance.
___
dri-devel mailing
https://bugzilla.kernel.org/show_bug.cgi?id=200695
Claude Heiland-Allen (cla...@mathr.co.uk) changed:
What|Removed |Added
Kernel Version|4.17.19, 4.18.5 through |4.17.19, 4.18.
Am Sonntag, 13. Januar 2019, 09:47:43 CET schrieb Julia Lawall:
> The device node iterators perform an of_node_get on each iteration, so a
> jump out of the loop requires an of_node_put.
>
> The semantic patch that fixes this problem is as follows
> (http://coccinelle.lip6.fr):
>
> //
> @@
> exp
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 new functions and use it across
the drivers.
vm_insert_ran
In the linux kernel MAINTAINERS file, largely
"xen-de...@lists.xenproject.org (moderated for non-subscribers)"
is used to refer to the xen-devel mailing list.
The DRM DRIVERS FOR XEN section entry mentions
xen-de...@lists.xen.org instead, but that is just the same
mailing list as the mailing lis
On 2019-01-10 18:48, Boris Brezillon wrote:
> On Thu, 10 Jan 2019 15:10:39 +
> Peter Rosin wrote:
>
>> The destination crtc rectangle is independent of source plane rotation.
>>
>> Signed-off-by: Peter Rosin
>> ---
>> drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c | 3 ---
>> 1 file change
Make the code easier to read and modify.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/bridge/lvds-encoder.c | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/bridge/lvds-encoder.c
b/drivers/gpu/drm/bridge/lvds-encoder.c
index 75b0d3f6e4de
Optionally power down the LVDS-encoder when it is not in use.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/bridge/lvds-encoder.c | 34 ++
1 file changed, 34 insertions(+)
diff --git a/drivers/gpu/drm/bridge/lvds-encoder.c
b/drivers/gpu/drm/bridge/lvds-encoder.
Sorry for that I missed typing 'd' in the email addreslist.
On 2019/1/10 20:52, Zheng Xiang wrote:
> Hi all,
>
> Recently I encountered a problem that virtio-gpu driver would have a very low
> chance of getting hung
> when I boot VM from linux kernel 4.19 on ARM64 server by using qemu. The
> dm
The name powerdown-gpios is the standard property name for the
functionality covered by the previous pwdn-gpios name. This rename
should be safe to do since the linux driver supporting the binding
(lvds-encoder.c) never implemented the property, and no dts file
names it. At least not upstream.
Rev
like Daniel guessed, fb-console does not work with this Patch.
i tried your Patch (additional patch for headerfile):
https://github.com/frank-w/BPI-R2-4.14/commits/4.20-fbdev
and R2 hangs (no crash and no further boot)
[5.435075] mediatek-drm 1400.dispsys: bound 14012000.rdma (ops mtk_
On 11/01/2019 at 14:29, Peter Rosin wrote:
> On 2019-01-10 18:48, Boris Brezillon wrote:
>> On Thu, 10 Jan 2019 15:10:39 +
>> Peter Rosin wrote:
>>
>>> The destination crtc rectangle is independent of source plane rotation.
>>>
>>> Signed-off-by: Peter Rosin
>>> ---
>>> drivers/gpu/drm/atme
On 2019-01-10 21:16, Sam Ravnborg wrote:
> Hi Peter.
>
> (Hijacking this thread as I lost the orginal mails)
Assuming you wanted to reply to this patch?
https://patchwork.kernel.org/patch/10753571/
>>> I found an unfortunate issue while recoding plane handling to use
>>> drm_atomic_helper_check_
On 10/01/2019 at 18:45, Boris Brezillon wrote:
> On Thu, 10 Jan 2019 15:10:28 +
> Peter Rosin wrote:
>
>> Hi!
>>
>> I found an unfortunate issue while recoding plane handling to use
>> drm_atomic_helper_check_plane_state(). The driver rotates clockwise,
>> which is not correct. I simply fixed
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 new functions and use it across
the drivers.
vm_insert_ran
Hi!
I'm not sure if I should have added the texas chips to the lvds_encoder_match
list in the driver, right next to the thine,thc63lvdm83d entry, but ended
up not doing that. That can always be added later, if needed...
Changes since v3:
- retained a (modified) note in lvds-transmitter.txt about
On Sat, Jan 12, 2019 at 12:27:05PM -0600, Shiraz Saleem wrote:
> On Fri, Jan 04, 2019 at 10:35:43PM +, Jason Gunthorpe wrote:
> > Commit 2db76d7c3c6d ("lib/scatterlist: sg_page_iter: support sg lists w/o
> > backing pages") introduced the sg_page_iter_dma_address() function without
> > providin
https://bugs.freedesktop.org/show_bug.cgi?id=107296
--- Comment #7 from Paul Menzel ---
I am still getting this error with Linux 5.0-rc1+.
[ 19.518149] WARNING: CPU: 2 PID: 359 at
drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1380
dcn_bw_update_from_pplib+0x158/0x
290 [amdgpu]
Convert to use vm_insert_range() to map range of kernel
memory to user vma.
Signed-off-by: Souptick Joarder
---
drivers/gpu/drm/xen/xen_drm_front_gem.c | 18 +-
1 file changed, 5 insertions(+), 13 deletions(-)
diff --git a/drivers/gpu/drm/xen/xen_drm_front_gem.c
b/drivers/gpu/d
DS90C185 has a shutdown pin which does not fit in the lvds-transmitter
binding, which is meant to be generic.
The sister chip DS90C187 is similar to DS90C185, describe it here as well.
Signed-off-by: Peter Rosin
---
.../bindings/display/bridge/lvds-transmitter.txt | 10 ++--
.../bindings/disp
Convert to use vm_insert_range() to map range of kernel
memory to user vma.
Signed-off-by: Souptick Joarder
---
drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_gem.c
b/driver
Drop #address-cells and #size-cells from the root node in the
example, they are unused.
Reviewed-by: Rob Herring
Signed-off-by: Peter Rosin
---
Documentation/devicetree/bindings/display/bridge/lvds-transmitter.txt | 2 --
1 file changed, 2 deletions(-)
diff --git
a/Documentation/devicetree/bi
On 2019-01-10 20:25, Boris Brezillon wrote:
> On Thu, 10 Jan 2019 18:51:21 +
> Peter Rosin wrote:
>
>> On 2019-01-10 18:29, Boris Brezillon wrote:
>>> On Thu, 10 Jan 2019 15:10:48 +
>>> Peter Rosin wrote:
>>>
The A2Q and UPDATE bits have no effect in the channel disable registers
https://bugs.freedesktop.org/show_bug.cgi?id=109331
--- Comment #7 from andrew.m.mcma...@gmail.com ---
Created attachment 143088
--> https://bugs.freedesktop.org/attachment.cgi?id=143088&action=edit
mesa-git glxinfo
As a last ditch effort I thought I'd try the latest mesa/llvm that are provided
https://bugs.freedesktop.org/show_bug.cgi?id=109124
--- Comment #2 from Sylvain BERTRAND ---
The actual main issue is while turning: since fps drops badly, it makes
turning all blury, then makes it quite harder to spot anything. And in "open
space" we turn all the time to check out if nobody is a
The actual main issue is while turning: since fps drops badly, it makes
turning all blury, then makes it quite harder to spot anything. And in "open
space" we turn all the time to check out if nobody is around (if you cannot
know you are alone in your tile). I run the 3d engine at 1920x1080, video
https://bugs.freedesktop.org/show_bug.cgi?id=105530
--- Comment #19 from Tyson Tan ---
I can confirm the screen stuttering with RX460 and RX550. It doesn't happen
with R7 250E or Firepro W5100 which are GCN2 cards using radeon. Seems to be a
Polaris/AMDGPU specific problem? This issue did not hap
https://bugs.freedesktop.org/show_bug.cgi?id=109182
Sylvain BERTRAND changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=109331
--- Comment #6 from andrew.m.mcma...@gmail.com ---
One last comment before I leave it to the experts.
Another bug report with Unity 18.04:
https://steamcommunity.com/app/10500/discussions/0/3441214221460524307/
If anyone wants to go above and b
https://bugs.freedesktop.org/show_bug.cgi?id=109338
Bug ID: 109338
Summary: hdmi/displayport audio is a semitone lower when amdgpu
driver is used
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS
https://bugs.freedesktop.org/show_bug.cgi?id=109331
--- Comment #5 from andrew.m.mcma...@gmail.com ---
I've used apitrace (DEBUGGER="apitrace32 trace" steam steam://rungameid/10500)
to capture some trace files.
I'm able to replay them using apitrace replay [file] so I hope others are too.
I've
https://bugs.freedesktop.org/show_bug.cgi?id=109331
--- Comment #4 from andrew.m.mcma...@gmail.com ---
Created attachment 143086
--> https://bugs.freedesktop.org/attachment.cgi?id=143086&action=edit
dmesg -w
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=109331
andrew.m.mcma...@gmail.com changed:
What|Removed |Added
Attachment #143084|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=109331
--- Comment #2 from andrew.m.mcma...@gmail.com ---
Created attachment 143084
--> https://bugs.freedesktop.org/attachment.cgi?id=143084&action=edit
Xorg log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=109336
Bug ID: 109336
Summary: gma500_gfx misdetects LVDS-1 as connected causing
black screen
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux
https://bugs.freedesktop.org/show_bug.cgi?id=109327
Bas Nieuwenhuizen changed:
What|Removed |Added
QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
Add an of_node_put when the result of of_graph_get_remote_port_parent is
not available.
The semantic match that finds this problem is as follows
(http://coccinelle.lip6.fr):
//
@r exists@
local idexpression e;
expression x;
@@
e = of_graph_get_remote_port_parent(...);
... when != x = e
when
Add an of_node_put when the result of of_graph_get_remote_port_parent is
not available.
An of_node_put is also needed when meson_probe_remote completes. This was
present at the recursive call, but not in the call from meson_drv_probe.
The semantic match that finds this problem is as follows
(htt
The result of of_graph_get_remote_port_parent needs an of_node_put,
even if it is not available.
---
drivers/gpu/drm/meson/meson_drv.c |9 +++--
drivers/gpu/drm/rcar-du/rcar_du_kms.c |1 +
drivers/of/property.c |1 +
3 files changed, 9 insertions(+), 2 deletio
The device node iterators perform an of_node_get on each iteration, so a
jump out of the loop requires an of_node_put.
The semantic patch that fixes this problem is as follows
(http://coccinelle.lip6.fr):
//
@@
expression root,e;
local idexpression child;
iterator name for_each_child_of_node;
@@
The device node iterators perform an of_node_get on each
iteration, so a jump out of the loop requires an of_node_put.
Remote and port also have augmented reference counts, so drop them
on each iteration and at the end of the function, respectively.
Remote is only used for the address it contains,
The device node iterators perform an of_node_get on each
iteration, so a jump out of the loop requires an of_node_put.
Move the initialization channel->child = child; down to just
before the call to imx_ldb_register so that intervening failures
don't need to clear it. Add a label at the end of th
The device node iterators perform an of_node_get on each iteration, so a
jump out of the loop requires an of_node_put.
The semantic patch that fixes this problem is as follows
(http://coccinelle.lip6.fr):
//
@@
local idexpression n;
expression e,e1;
identifier l;
@@
for_each_child_of_node(e1,n
The device node iterators perform an of_node_get on each iteration, so a
jump out of the loop requires an of_node_put.
The patches for drivers/gpu/drm/imx/imx-ldb.c and
drivers/gpu/drm/sun4i/sun4i_backend.c contain some added of_node_puts for
which the need was identified manually. Details are in
https://bugzilla.kernel.org/show_bug.cgi?id=201273
--- Comment #29 from quirin.blae...@freenet.de ---
Bug is still alive. amd-staging-drm-next
9698024e8a191481321574bec1fe886bbce797cf
--
You are receiving this mail because:
You are watching the assignee of the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=109327
--- Comment #2 from Ahmed Elsayed ---
To be more accurate. The game doesn't crash. It stuck at black screen after
skipping the first cutscene.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=109327
Ahmed Elsayed changed:
What|Removed |Added
Summary|Wolfenstein II The New |Wolfenstein II The New
70 matches
Mail list logo
