On 2016年09月08日 21:41, Christian König wrote:
From: Christian König
Either never used or not used in quite a while.
No, I remember Flora's Direct GMA is using them like GDS use PRIV0-2.
And you cannot make sure there isn't no one using them in other closed
projects, right?
If you removed now
Hi Flora:
What is the purpose of these patches?
Thanks
JimQu
发件人: amd-gfx 代表 Flora Cui
发送时间: 2016年9月9日 14:30:51
收件人: amd-gfx@lists.freedesktop.org
抄送: Cui, Flora
主题: [PATCH 2/2] drm/amdgpu: calc addr with domain's gpu_offset
Change-Id: I8112e9d8586610
Change-Id: Ia2cb8a8f62d0933b7937991bec4eace560745f97
Signed-off-by: Flora Cui
---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
index 5a6216c
Change-Id: I8112e9d85866104559ecef7449f50fbb94167382
Signed-off-by: Flora Cui
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
index a549abd..3d7a3ab 1006
On 09/09/16 01:23 AM, Chris Wilson wrote:
> On Thu, Sep 08, 2016 at 05:21:42PM +0200, Mario Kleiner wrote:
>> On 09/08/2016 08:30 AM, Chris Wilson wrote:
>>> On Thu, Sep 08, 2016 at 02:14:43AM +0200, Mario Kleiner wrote:
amdgpu-kms uses shared fences for its prime exported dmabufs,
instea
This fix is for the following xorg.conf can work:
Section "ServerFlags"
Option "AutoAddGPU" "off"
EndSection
Section "Device"
Identifier "Amd"
Driver "ati"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Intel"
Driver "modesetting"
> -Original Message-
> From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf
> Of Michel Dänzer
> Sent: Thursday, September 08, 2016 6:03 AM
> To: amd-gfx@lists.freedesktop.org
> Subject: [PATCH xf86-video-amdgpu 12/12] Make TearFree effective with
> PRIME slave scanout
>
> -Original Message-
> From: Qu, Jim
> Sent: Thursday, September 08, 2016 4:51 AM
> To: Deucher, Alexander; amd-gfx@lists.freedesktop.org
> Subject: 答复: [PATCH v2] drm/amd/amdgpu: S4 issue for amdgpu
>
> Hi Alex:
>
> According to my understanding, in our driver,
> amdgpu_device_suspend/re
> -Original Message-
> From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf
> Of Rex Zhu
> Sent: Thursday, September 08, 2016 2:05 AM
> To: amd-gfx@lists.freedesktop.org
> Cc: Zhu, Rex
> Subject: [PATCH 2/3] drm/amdgpu: fix compiler warning.
>
> no parentheses around assi
From: Michel Dänzer
TearFree can now prevent tearing with any possible display
configuration.
Note that there may still be inter-GPU tearing if the primary GPU uses
a different driver.
(Ported from radeon commit 38797a33117222dadbc89e5f21ed8cd5deef9bea)
Signed-off-by: Michel Dänzer
---
src/a
From: Michel Dänzer
Copy the damaged areas which are still valid in the other scanout pixmap
from there, then only copy the remaining damaged area from the screen
pixmap.
This is slightly more efficient (only needs one Damage record instead of
two, and only needs to copy each screen update acros
From: Michel Dänzer
Will be needed higher up by the following changes. No functional change.
(Ported from radeon commit 2f6e5fb15f1a9ce523c85550e493f8bda9d0c00f)
Signed-off-by: Michel Dänzer
---
src/amdgpu_kms.c | 34 +-
1 file changed, 17 insertions(+), 17 del
From: Michel Dänzer
Only copy once for each time we update the corresponding scanout pixmap.
This can significantly reduce the bandwidth usage when there are
frequent updates to the screen pixmap.
This initial implementation only works when both the master and slave
screens use this driver.
(Po
From: Michel Dänzer
Should make the amdgpu_drm_queue_alloc error handling clearer, and gets
rid of a compile warning about it returning NULL.
(Ported from radeon commit a37af701768b12d86868a831a79f1e02ee4968cf)
Signed-off-by: Michel Dänzer
---
src/amdgpu_dri2.c | 4 ++--
src/amdgpu_drm_q
From: Michel Dänzer
At least with older kernels, the flip may never complete otherwise,
which can result in us hanging in drmmode_set_mode_major.
Fixes:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170
(Ported from radeon commits 9090309e057dc703d1a5bffd88e6cae1410
From: Michel Dänzer
(Ported from radeon commit 5a57005178fc13b6f7e513458ca6dae72a3e5783)
Signed-off-by: Michel Dänzer
---
src/amdgpu_kms.c | 74
1 file changed, 43 insertions(+), 31 deletions(-)
diff --git a/src/amdgpu_kms.c b/src/amdgp
From: Michel Dänzer
This further reduces the PCIe bandwidth usage.
(Ported from radeon commit b0867063abb197b9134166706d99fcbe5f204bb5,
plus leak fix from 5a57005178fc13b6f7e513458ca6dae72a3e5783)
Signed-off-by: Michel Dänzer
---
src/amdgpu_kms.c | 83
From: Michel Dänzer
This further reduces the compositing slowdown due to flushing overhead,
by only flushing when the X server actually sends XDamageNotify events
to a client, and there hasn't been a flush yet in the meantime.
(Ported from radeon commit 121a6de72da5fcf9a32408eff36b2235f3dfbcfe)
From: Michel Dänzer
This should allow using multiple CRTCs via RandR 1.4 even with xserver
< 1.17. It also simplifies the code a little, and paves the way for
following changes.
(Ported from radeon commits 4cfa4615f79f64062e5e771cd45dd7048f48b4f6
and a92c27484703abc7c410b6ae0e4b8d1efbbb8e6f)
S
From: Michel Dänzer
This reduces PCIe bandwidth usage and tearing.
(Ported from radeon commit ad0a0656dd0e74683e6d7789decba827aa29c221)
Signed-off-by: Michel Dänzer
---
src/amdgpu_kms.c | 96 ++--
1 file changed, 93 insertions(+), 3 deletion
From: Michel Dänzer
We only need to flush for XDamageNotify events.
Significantly reduces compositing slowdown due to flushing overhead, in
particular with glamor.
(Ported from radeon commit 9a1afbf61fbb2827c86bd86d295fa0848980d60b)
Signed-off-by: Michel Dänzer
---
src/amdgpu_drv.h| 2 +
Hi Alex:
According to my understanding, in our driver, amdgpu_device_suspend/resume. the
paremeter 'suspend' or 'resume' mean the apdpter is set to D3, and we need
power on it at resume. In S4 , the function freeze() , thraw() , poweroff() and
restore() is special for hibernation, S3 process c
Am 08.09.2016 um 09:35 schrieb Chris Wilson:
On Thu, Sep 08, 2016 at 03:22:48PM +0800, Huang Rui wrote:
On Thu, Sep 08, 2016 at 02:36:06PM +0800, Chris Wilson wrote:
On Wed, Sep 07, 2016 at 10:07:57PM -0400, Huang Rui wrote:
In previous drm_global_item_ref, there are two times of writing
ref->
Am 08.09.2016 um 04:07 schrieb Huang Rui:
In previous drm_global_item_ref, there are two times of writing
ref->object if item->refcount is 0. So this patch does a minor update
to put alloc and init ref firstly, and then to modify the item of glob
array. Use "else" to avoid two times of writing re
On Thu, Sep 08, 2016 at 02:36:06PM +0800, Chris Wilson wrote:
> On Wed, Sep 07, 2016 at 10:07:57PM -0400, Huang Rui wrote:
> > In previous drm_global_item_ref, there are two times of writing
> > ref->object if item->refcount is 0. So this patch does a minor update
> > to put alloc and init ref firs
Am 08.09.2016 um 08:32 schrieb Monk Liu:
v1:
for gfx8, use CONTEXT_CONTROL package to dynamically
skip preamble CEIB and other load_xxx command in sequence.
v2:
support GFX7 as well, and bump up version.
remove cntxcntl in compute ring funcs because CPC doesn't
support this packet.
v3: fix redu
26 matches
Mail list logo
