https://bugzilla.kernel.org/show_bug.cgi?id=193651
--- Comment #28 from fin4...@hotmail.com ---
(In reply to Alex Deucher from comment #11)
> (In reply to fin4478 from comment #8)
> > Alex, thanks for the new firmware. Still Bios recognition errors at boot,
> > but otherwise ok.
> >
> > [3.46
+ Horace
-Original Message-
From: Colin King [mailto:colin.k...@canonical.com]
Sent: 2017年11月11日 19:51
To: Deucher, Alexander ; Koenig, Christian
; David Airlie ; Liu, Monk
; Yu, Xiangliang ;
amd-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org
Cc: kernel-janit...@vger.kernel
Hi all,
On Mon, 30 Oct 2017 20:37:56 + Mark Brown wrote:
>
> Today's linux-next merge of the devicetree tree got a conflict in:
>
> drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c
>
> between commit:
>
> 44cd3939c111b7 ("drm/tilcdc: Remove redundant OF_DETACHED flag setting")
>
> from th
Hi Marek,
2017년 11월 10일 16:35에 Marek Szyprowski 이(가) 쓴 글:
> Dear Inki,
>
> On 2017-11-10 04:04, Inki Dae wrote:
>> 2017년 11월 01일 01:28에 Marek Szyprowski 이(가) 쓴 글:
>>> When no IOMMU is available, all GEM buffers allocated by Exynos DRM driver
>>> are contiguous, because of the underlying dma_alloc
https://bugs.freedesktop.org/show_bug.cgi?id=103700
Hein-Pieter van Braam changed:
What|Removed |Added
Version|XOrg git|unspecified
--
You are receivi
https://bugs.freedesktop.org/show_bug.cgi?id=103700
--- Comment #1 from Hein-Pieter van Braam ---
I forgot to mention: I run Fedora 27 in userspace with Xorg.
The following package versions may be relevant:
xorg-x11-server-Xorg-1.19.5-1.fc27.x86_64
xorg-x11-drv-amdgpu-1.3.0-3.fc27.x86_64
mesa-d
https://bugs.freedesktop.org/show_bug.cgi?id=103700
Bug ID: 103700
Summary: Displayport link status failed on resume from suspend
on eDP on RX580 with Asus GL702ZC
Product: DRI
Version: XOrg git
Hardware: Other
https://bugs.freedesktop.org/show_bug.cgi?id=103697
Bas Nieuwenhuizen changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #16 from mikhail.v.gavri...@gmail.com ---
> Interesting, that indeed that should work. Could be a bug in the VESA BIOS or
> the driver touching the hardware even if it decided not to do so.
> Please try booting with modprobe.blackli
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #15 from Christian König ---
(In reply to mikhail.v.gavrilov from comment #13)
> a. Intel Graphics Processor -> Enabled
> b. Initial display output -> PCIe 2 slot
> c. A monitor connected to Radeon
> BIOS screenshot: https://bugs.fre
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #14 from mikhail.v.gavri...@gmail.com ---
The alternative is to use AMDs DKMS package for the closed source driver, but
that is targeted mostly for server compute as well and I don't know how well
that works with a desktop card.
This
https://bugs.freedesktop.org/show_bug.cgi?id=100069
--- Comment #3 from Gregor Münch ---
Still a thing with current git.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #13 from mikhail.v.gavri...@gmail.com ---
> You need to use Alex amd-staging-drm-next kernel or wait for 4.15.
Where I can find such kernel or patch set for 4.13 or 4.14 kernel?
> That's because in this configuration the BIOS brings
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #12 from mikhail.v.gavri...@gmail.com ---
Created attachment 135428
--> https://bugs.freedesktop.org/attachment.cgi?id=135428&action=edit
case 3 (Intel Graphics Processor -> Disabled, Initial display output -> PCIe 2
slot)
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #11 from mikhail.v.gavri...@gmail.com ---
Created attachment 135427
--> https://bugs.freedesktop.org/attachment.cgi?id=135427&action=edit
case 2 (Intel Graphics Processor -> Enabled, Initial display output -> PCIe 2
slot)
--
You a
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #10 from mikhail.v.gavri...@gmail.com ---
Created attachment 135426
--> https://bugs.freedesktop.org/attachment.cgi?id=135426&action=edit
case 1 (Intel Graphics Processor -> Enabled, The initial display output ->
IGGX)
--
You are
Deleted BOs with the same reservation object can be reaped even if they
can't be reserved.
v2: rebase and we still need to remove/add the BO from/to the LRU.
v3: fix remove/add one more time, cleanup the logic a bit
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 55 ++
Needed for the next patch.
v2: actually predicate all unlocks
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 59 +---
1 file changed, 33 insertions(+), 26 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm
https://bugs.freedesktop.org/show_bug.cgi?id=103697
Kenneth Graunke changed:
What|Removed |Added
Assignee|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=100306
--- Comment #43 from MirceaKitsune ---
I'm sorry for having taken so long to get back to this issue: I needed to be
sure that what I'm mentioning is correct, which at this point took months of
verification to be certain the issue is gone for goo
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #9 from Christian König ---
(hitting send to early, sorry) but you still need to compile the kernel on your
own.
The alternative is to use AMDs DKMS package for the closed source driver, but
that is targeted mostly for server comput
https://bugs.freedesktop.org/show_bug.cgi?id=103678
Christian König changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mai
https://bugs.freedesktop.org/show_bug.cgi?id=103678
Christian König changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #7 from mikhail.v.gavri...@gmail.com ---
Created attachment 135421
--> https://bugs.freedesktop.org/attachment.cgi?id=135421&action=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=103678
--- Comment #6 from mikhail.v.gavri...@gmail.com ---
Created attachment 135420
--> https://bugs.freedesktop.org/attachment.cgi?id=135420&action=edit
system log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=103678
mikhail.v.gavri...@gmail.com changed:
What|Removed |Added
Status|CLOSED |REOPENED
Resoluti
A few comments on the code:
+/* Validate bo size is bit bigger then the request domain */
+static inline bool amdgpu_bo_validate_bo_size(struct amdgpu_device *adev,
+ unsigned long size, u32 domain)
Drop the inline keyword and the second _bo_ in the name here.
+{
+ str
Am 10.11.2017 um 08:22 schrieb Chunming Zhou:
On 2017年11月09日 16:59, Christian König wrote:
Deleted BOs with the same reservation object can be reaped even if they
can't be reserved.
v2: rebase and we still need to remove/add the BO from/to the LRU.
Signed-off-by: Christian König
---
drive
Good catch and yeah that is actually the real problem why my original
patch didn't worked as expected.
Going to fix this in v2,
Christian.
Am 10.11.2017 um 10:55 schrieb He, Roger:
static int ttm_bo_cleanup_refs(struct ttm_buffer_object *bo,
bool interruptible, b
https://bugs.freedesktop.org/show_bug.cgi?id=103678
Christian König changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=103678
Christian König changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mai
31 matches
Mail list logo
