The display-timing and delay are included in the panel driver. So it
should be removed in dts.
Signed-off-by: Hoegeun Kwon
---
Hi Krzysztof,
This patch was rebased to the mainline (v4.14-rc1).
Best regards,
Hoegeun
arch/arm/boot/dts/exynos3250-rinato.dts | 22
On 2017年09月15日 16:36, Haneen Mohammed wrote:
This patch replace instances of dev_info/err/debug with
DRM_DEV_INFO/ERROR/WARN respectively inorder to use a drm-formatted
specific log messages. Issue corrected with the help of the following
Coccinelle script:
@r@
@@
(
-dev_info
+DRM_DEV_INFO
|
https://bugs.freedesktop.org/show_bug.cgi?id=102683
Niklas Haas changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=102820
--- Comment #5 from dwagner ---
Two additional remarks:
- I meanwhile verified that X runs fine when I compile the current
amd-staging-drm-next with only commit ebbf7337e2daacacef3e01114e6be68a2a4f11b4
reverted.
- The
https://bugs.freedesktop.org/show_bug.cgi?id=102820
--- Comment #4 from dwagner ---
I attached the Xorg.0.log as requested, the "dmesg" output as a whole would be
somewhat hard to edit for potentially sensitive content, thus I filtered it
through "grep -i -w -e drm -e
https://bugs.freedesktop.org/show_bug.cgi?id=102820
--- Comment #3 from dwagner ---
Created attachment 134300
--> https://bugs.freedesktop.org/attachment.cgi?id=134300=edit
dmesg (filtered by "grep -i -w -e drm -e amdgpu")
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=102820
--- Comment #2 from dwagner ---
Created attachment 134299
--> https://bugs.freedesktop.org/attachment.cgi?id=134299=edit
Xorg.0.log written while symptoms of Bug 102820 occur
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=102820
--- Comment #1 from Alex Deucher ---
Please attach your xorg log, dmesg output, and xorg conf if you are using one.
--
You are receiving this mail because:
You are the assignee for the
On Sat, Sep 16, 2017 at 11:58 AM, Oded Gabbay wrote:
> On Mon, Sep 4, 2017 at 10:50 AM, Daniel Vetter wrote:
>> Hi Alex,
>>
>> Since Dave is out, can you just pull that into the amd pile?
>> -Daniel
>>
>
> Hi Alex,
> Did you take the patches to your pile ?
https://bugs.freedesktop.org/show_bug.cgi?id=102358
--- Comment #22 from har...@gmx.de ---
Created attachment 134297
--> https://bugs.freedesktop.org/attachment.cgi?id=134297=edit
debug log: concurrent waiting in xcb_wait_for_special_event()
This command's are used for logging (all in
https://bugs.freedesktop.org/show_bug.cgi?id=102358
--- Comment #21 from har...@gmx.de ---
... looks like the reason for freezing, is a concurrent waiting in
xcb_wait_for_special_event(..).
While the main thread is waiting for present related events, another thread is
consuming this events
https://bugs.freedesktop.org/show_bug.cgi?id=101483
--- Comment #13 from FFAB ---
Upstream kernel test - kernel 4.14-rc1
Installation, on which upstream kernel was installed:
ubuntu 16.04.3, kernel4.10.0-33, updated 2017-09-17
1. booting without any workaround parameters
2.
https://bugs.freedesktop.org/show_bug.cgi?id=101483
FFAB changed:
What|Removed |Added
Attachment #133777|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=101483
FFAB changed:
What|Removed |Added
Attachment #133857|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=100387
--- Comment #17 from Maksim ---
(In reply to aceman from comment #6)
> Are those problems solved in radeonsi?
(In reply to aceman from comment #10)
> I asked about the radeonSI drive in comment 6 but didn't get a
https://bugs.freedesktop.org/show_bug.cgi?id=100387
Maksim Bobylev changed:
What|Removed |Added
Version|git |17.1
---
https://bugs.freedesktop.org/show_bug.cgi?id=101900
Frederik changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=102814
--- Comment #4 from Luke A. Guest ---
Turn on triple buffering, this is an old issue that's been reported before.
--
You are receiving this mail because:
You are the assignee for the
On Fri, Sep 8, 2017 at 5:13 PM, Colin King wrote:
> From: Colin Ian King
>
> The call to kfd_device_by_id can potentially return null, so check that
> dev is null and return with -EINVAL to avoid a null pointer dereference.
>
> Detected by
https://bugs.freedesktop.org/show_bug.cgi?id=102389
--- Comment #8 from jeremi.jasin...@gmail.com ---
Thank you for your response. I've tried two different cables, and none of them
fixed the problem.
I will buy dedicated 4k 60hz cable and see if theres any difference.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=102820
Bug ID: 102820
Summary: [bisected] commit
ebbf7337e2daacacef3e01114e6be68a2a4f11b4 prevents X11
from starting
Product: DRI
Version: DRI git
Hardware:
https://bugs.freedesktop.org/show_bug.cgi?id=102814
--- Comment #3 from freedesk...@ca.sh13.net ---
Indeed, that solves the issue. I guess this needs to be filed with Blender
then?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102389
--- Comment #7 from dwagner ---
Just a thought: The symptom you describe ("random black screen, lasting for 1-2
seconds") can be caused by bad HDMI cables - especially when using 4k / 60Hz
modes - I had experienced that in
From: Hans Verkuil
Add an entry for the CEC GPIO driver.
Signed-off-by: Hans Verkuil
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index eb930ebecfcb..5ef0d34ef502 100644
--- a/MAINTAINERS
From: Hans Verkuil
Document the bindings for the cec-gpio module for hardware where the
CEC line and optionally the HPD line are connected to GPIO lines.
Signed-off-by: Hans Verkuil
Reviewed-by: Linus Walleij
---
From: Hans Verkuil
Add support for two new low-level events: PIN_HPD_LOW and PIN_HPD_HIGH.
This is specifically meant for use with the upcoming cec-gpio driver
and makes it possible to trace when the HPD pin changes. Some HDMI
sinks do strange things with the HPD and
From: Hans Verkuil
Document these new CEC events.
Signed-off-by: Hans Verkuil
---
Documentation/media/uapi/cec/cec-ioc-dqevent.rst | 18 ++
1 file changed, 18 insertions(+)
diff --git
From: Hans Verkuil
Add a simple HDMI CEC GPIO driver that sits on top of the cec-pin framework.
While I have heard of SoCs that use the GPIO pin for CEC (apparently an
early RockChip SoC used that), the main use-case of this driver is to
function as a debugging tool.
By
From: Hans Verkuil
This driver adds support for CEC implementations that use a pull-up
GPIO line. While SoCs exist that do this, the primary use-case is to
turn a single-board computer into a cheap CEC debugger.
Together with 'cec-ctl --monitor-pin' you can do low-level
On Sat, Sep 16, 2017 at 4:28 PM, Hans Verkuil wrote:
> From: Hans Verkuil
>
> Add a simple HDMI CEC GPIO driver that sits on top of the cec-pin framework.
>
> While I have heard of SoCs that use the GPIO pin for CEC (apparently an
> early RockChip SoC
On Sat, Sep 16, 2017 at 4:28 PM, Hans Verkuil wrote:
> From: Hans Verkuil
>
> Document the bindings for the cec-gpio module for hardware where the
> CEC line and optionally the HPD line are connected to GPIO lines.
>
> Signed-off-by: Hans Verkuil
Hi
Am 16.09.2017 23:41 schrieb "Torsten Sievers" :
Hi guys,
when i reading through the (somewhen) upcoming iMX8 and its GC7000 series i
stumbled over this one:
http://www.vivantecorp.com/index.php/en/technology/3d.html
at the very end it is stating the the
https://bugzilla.kernel.org/show_bug.cgi?id=196777
--- Comment #9 from Krzysztof Nowicki (kri...@op.pl) ---
(In reply to Gerd Hoffmann from comment #8)
> https://www.kraxel.org/cgit/linux/log/?h=qxl-4.13
> please test
Applied over vanilla 4.12 on top of the patch from comment #2.
SDDM started
https://bugs.freedesktop.org/show_bug.cgi?id=102814
--- Comment #2 from network...@rkmail.ru ---
I think it's related to bug #98784, try starting blender with
LIBGL_DRI3_DISABLE=1
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102814
--- Comment #1 from freedesk...@ca.sh13.net ---
Should be of course "... the recently released Blender 2.79 doesn't work with
Mesa 17.2 at all ...", a kingdom for an edit button :)
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=102814
Bug ID: 102814
Summary: Blender 2.79 flickering
Product: Mesa
Version: 17.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
36 matches
Mail list logo