On Fri, Jun 15, 2018 at 11:38:44PM +0300, Ville Syrjälä wrote:
> On Wed, May 30, 2018 at 11:22:27PM +0300, Ville Syrjälä wrote:
> > On Wed, May 30, 2018 at 06:30:52PM +0100, Alexandru Gheorghe wrote:
> > > drm_private_state has a back pointer to the drm_atomic_state,
> > > however that was not
The wrong enum type is used to initialize the result, leading to a
warning when using clang:
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:1998:26: warning:
implicit conversion from enumeration type 'enum ddc_result' to different
enumeration type 'enum dc_status'
Explicitly use the first uvd instance to avoid a build error when
using clang 6:
drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c:1148:52: error: expected ')'
container_of(work, struct amdgpu_device,
uvd.inst->idle_work.work);
The limit_id_fallback array uses enum drm_ipp_size_id to index its
content. The content itself is of type enum drm_exynos_ipp_limit_type.
Cc: Marek Szyprowski
Signed-off-by: Stefan Agner
---
drivers/gpu/drm/exynos/exynos_drm_ipp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Sun, 17 Jun 2018 10:48:22 +0200
Stefan Agner wrote:
> The statement always evaluates to true since the struct fields
> are arrays. This has shown up as a warning when compiling with
> clang:
> warning: address of array 'desc->layout.xstride' will always
> evaluate to 'true'
https://bugs.freedesktop.org/show_bug.cgi?id=104274
--- Comment #16 from Sverd Johnsen ---
hmm this is new
[41889.542562] Console: switching to colour dummy device 80x25
[41890.859216] [drm] amdgpu: finishing device.
[41891.096266] [TTM] Finalizing pool allocator
[41891.100313] [TTM] Finalizing
https://bugs.freedesktop.org/show_bug.cgi?id=106938
Bug ID: 106938
Summary: Module *radeon* takes over two seconds to load
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity:
On Sun, 17 Jun 2018 01:34:34 +0200
Stefan Agner wrote:
> Boris, Maxime,
>
> On 07.08.2017 08:26, Stefan Agner wrote:
> > The statement always evaluates to true since the struct fields
> > are arrays. This has shown up as a warning when compiling with
> > clang:
> > warning: address of array
https://bugs.freedesktop.org/show_bug.cgi?id=105083
denisgolo...@yandex.ru changed:
What|Removed |Added
Status|REOPENED|RESOLVED
The statement always evaluates to true since the struct fields
are arrays. This has shown up as a warning when compiling with
clang:
warning: address of array 'desc->layout.xstride' will always
evaluate to 'true' [-Wpointer-bool-conversion]
Check for values in the first plane instead.
https://bugzilla.kernel.org/show_bug.cgi?id=199749
--- Comment #9 from notsyncing (song...@gmail.com) ---
I found I'm able to reproduce the freeze when I'm compiling two Android ROMs at
the same time while browsing or something else. It will freeze in at most 3
hours. I have a 300W PSU, and 2 SSD
https://bugs.freedesktop.org/show_bug.cgi?id=106938
--- Comment #2 from Paul Menzel ---
Is that a firmware or hardware problem?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=106938
--- Comment #1 from Paul Menzel ---
Just to put this into perspective, that without loading the radeon module, the
OS, that means Linux kernel + user space, takes around two to three seconds to
start (substracting the LUKS passphrase dialog).
https://bugzilla.kernel.org/show_bug.cgi?id=199749
--- Comment #8 from notsyncing (song...@gmail.com) ---
Today I tried the amdgpu.vm_update_mode=3 option, and my computer still
freezed. This time no log was recorded.
--
You are receiving this mail because:
You are watching the assignee of the
This is a note to let you know that I've just added the patch titled
drm/msm: don't deref error pointer in the msm_fbdev_create error path
to the 4.16-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the
https://bugs.freedesktop.org/show_bug.cgi?id=106940
Bug ID: 106940
Summary: Black screen on KMS with 4.18.0-rc1 with Kaveri+Topaz,
amdgpu, dc=1
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS:
https://bugs.freedesktop.org/show_bug.cgi?id=106303
--- Comment #6 from Julian ---
Can confirm. I'm using a Rx 560 on kernel 4.16 and my clock rate is stuck on
1230MHz permanently.
I'm also using a single 2560x1440x144 monitor
This is directly related to DC. If I run with amdgpu.dc=0 the issue
https://bugs.freedesktop.org/show_bug.cgi?id=106942
Bug ID: 106942
Summary: X freezes with Ubuntu kernel 4.15.0-23-generic
(AMDGPU)
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=106940
--- Comment #1 from SET ---
This happens on both early and late KMS (Arch Linux).
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On Sun, 17 Jun 2018 10:48:22 +0200
Stefan Agner wrote:
> The statement always evaluates to true since the struct fields
> are arrays. This has shown up as a warning when compiling with
> clang:
> warning: address of array 'desc->layout.xstride' will always
> evaluate to 'true'
Hi Enric
2018-06-16 19:15 GMT+09:00 Enric Balletbo Serra :
> Hi Chanwoo,
>
> I'll send a new version soon, just wanted to ask some questions here. See
> below.
>
> Missatge de Chanwoo Choi del dia dt., 15 de
> maig 2018 a les 0:21:
>>
>> Hi,
>>
>> On 2018년 05월 15일 06:16, Enric Balletbo i Serra
A regression was reported via Bugzilla and a revert seems to be the best choice
for now. Check patch 1 for details. To not make the same mistake again, patch 2
adds a comment sharing our experience.
Wolfram Sang (2):
Revert "i2c: algo-bit: init the bus to a known state"
i2c: algos: bit:
So, if somebody wants to re-implement this in the future, we pinpoint to
a problem case.
Signed-off-by: Wolfram Sang
---
drivers/i2c/algos/i2c-algo-bit.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/i2c/algos/i2c-algo-bit.c b/drivers/i2c/algos/i2c-algo-bit.c
index
This reverts commit 3e5f06bed72fe72166a6778f630241a893f67799. As per
bugzilla #200045, this caused a regression. I don't really see a way to
fix it without having the hardware. So, revert the patch and I will fix
the issue I was seeing originally in the i2c-gpio driver itself. I
couldn't find new
This is a note to let you know that I've just added the patch titled
drm/msm: don't deref error pointer in the msm_fbdev_create error path
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the
Hi All,
Here is a patch-set to make sure that the efifb contains the boot
graphics from the ACPI BGRT extension when the kernel is configured
to use the (new) deferred fbcon console takeover support.
Let me explain why this is desirable (same reason as for the deferred
fbcon console takeover
On systems where fbcon is configured for deferred console takeover, the
intend is for the framebuffer to show the boot graphics (e.g a vendor
logo) until some message (e.g. an error) is printed or a graphical
session takes over.
Some firmware however relies on the OS to show the boot graphics
bgrt_image_size is necessary to (optionally) show the boot graphics from
the efifb code. The efifb driver is a platform driver, using a normal
driver probe() driver callback. So even though it is always builtin it
cannot reference __initdata.
Signed-off-by: Hans de Goede
---
https://bugs.freedesktop.org/show_bug.cgi?id=106820
Nick Sarnie changed:
What|Removed |Added
CC||commendsar...@gmail.com
--- Comment #2
On 2018-06-17 04:52 AM, Stefan Agner wrote:
Explicitly use the first uvd instance to avoid a build error when
using clang 6:
drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c:1148:52: error: expected ')'
container_of(work, struct amdgpu_device,
uvd.inst->idle_work.work);
From: Dave Airlie
Fixes: 9428088c (drm/qxl: reapply cursor after resetting primary)
Reported-by: Mike Galbraith
Cc: sta...@vger.kernel.org
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/qxl/qxl_display.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
Lyude bisected a similar problem on a much newer GPU to this very same
change as well. [Sorry, no useful information beyond that, but thought
I'd make the connection.]
On Sun, Jun 17, 2018 at 5:46 PM, Adam Borowski wrote:
> Hi!
> On v4.18-rc1, the mouse cursor is missing on my right monitor.
>
32 matches
Mail list logo
