https://bugs.freedesktop.org/show_bug.cgi?id=102962
--- Comment #13 from Timothy Arceri ---
(In reply to Tobias Auerochs from comment #12)
> (In reply to Timothy Arceri from comment #11)
> > (In reply to gloriouseggroll from comment #9)
> > > Created attachment 138466 [details]
> > > broken color
https://bugs.freedesktop.org/show_bug.cgi?id=105760
--- Comment #65 from Thomas Martitz ---
https://patchwork.kernel.org/patch/10583229/ (modified such that the quirk is
applied unconditionally) fixes GPU resume on my laptop as well. I think it's
got the same PCIe bridge as the ASUS machines ment
https://bugzilla.kernel.org/show_bug.cgi?id=195159
Peter Wu (pe...@lekensteyn.nl) changed:
What|Removed |Added
CC||pe...@lekensteyn.nl
---
https://bugs.freedesktop.org/show_bug.cgi?id=107793
--- Comment #9 from 8zst4a7dhsqbq...@tuta.io ---
Just to add - Same happens to me with an R9 380 graphics card since amdgpu.dc
was enabled. I am using my monitor through the vga port (with an dvi to vga
adapter on my gpu). Passing "amdgpu.dc=0" a
https://bugs.freedesktop.org/show_bug.cgi?id=107793
--- Comment #10 from ZLD <8zst4a7dhsqbq...@tuta.io> ---
Created attachment 141483
--> https://bugs.freedesktop.org/attachment.cgi?id=141483&action=edit
output of journalctl on failed boot with amdgpu.dc=1 amdgpu.dc_log=1
--
You are receiving
Improve error reporting in drm_fb_helper_fbdev_setup() by printing the
error code. This is useful for drivers that choose to not fall over just
because fbdev doesen't work, but still wants clues to why it failed.
This way they don't have to provide an error message themselves.
Signed-off-by: Noral
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
This patchset moves the drivers using the CMA helper fully over to the
generic fbdev emulation. The unused fbdev code is removed from the CMA
helper.
Noralf.
Noralf Trønnes (20):
drm/fb-helper: Improve error reporting in setup
drm/arc: Use drm_fbdev_generic_setup()
drm/fsl-dcu: Use drm_fbde
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
CMA helper drivers have been converted to drm_fbdev_generic_setup()
so the fbdev code can be removed.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/Kconfig | 4 -
drivers/gpu/drm/drm_fb_cma_helper.c | 151
include/drm/drm_fb_cma_helper.h
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
The CMA helper is already using the drm_fb_helper_generic_probe part of
the generic fbdev emulation. This patch makes full use of the generic
fbdev emulation by using its drm_client callbacks. This means that
drm_mode_config_funcs->output_poll_changed and drm_driver->lastclose are
now handled by th
Hi Ayan,
On 10/07/2018 15:18, Ayan Kumar Halder wrote:
> In the current series of patches, we are trying to add support for AFBC
> modifiers in malidp. AFBC modifiers adds some constraints to framebuffer
> size, alignment, pitch, formats, etc. Here we are trying to add support
> for one combinatio
https://bugs.freedesktop.org/show_bug.cgi?id=107858
--- Comment #2 from Lothar Paltins ---
Created attachment 141484
--> https://bugs.freedesktop.org/attachment.cgi?id=141484&action=edit
dmesg output before and after monitor power cycle
--
You are receiving this mail because:
You are the assi
https://bugs.freedesktop.org/show_bug.cgi?id=107858
--- Comment #3 from Lothar Paltins ---
Created attachment 141485
--> https://bugs.freedesktop.org/attachment.cgi?id=141485&action=edit
Xorg.0.log output before monitor power cycle
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=107858
--- Comment #4 from Lothar Paltins ---
Created attachment 141486
--> https://bugs.freedesktop.org/attachment.cgi?id=141486&action=edit
Xorg.0.log after monitor power cycle
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107858
--- Comment #6 from Lothar Paltins ---
Created attachment 141488
--> https://bugs.freedesktop.org/attachment.cgi?id=141488&action=edit
xrandr output after monitor power cycle
--
You are receiving this mail because:
You are the assignee for t
https://bugs.freedesktop.org/show_bug.cgi?id=107858
--- Comment #5 from Lothar Paltins ---
Created attachment 141487
--> https://bugs.freedesktop.org/attachment.cgi?id=141487&action=edit
xrandr output before monitor power cycle
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=107858
--- Comment #7 from Lothar Paltins ---
But the client must know the possible resolutions and this information must
come from the X server and the driver.
I'm using the KDE5 desktop environment and I've attached the appropriate log
files. The dm
https://bugs.freedesktop.org/show_bug.cgi?id=107867
Bug ID: 107867
Summary: The game The Evil Within Demo lead to GPU hang when
played first cut scene.
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=107867
--- Comment #1 from mikhail.v.gavri...@gmail.com ---
Created attachment 141491
--> https://bugs.freedesktop.org/attachment.cgi?id=141491&action=edit
hung cut scene photo
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freedesktop.org/show_bug.cgi?id=107867
--- Comment #2 from mikhail.v.gavri...@gmail.com ---
$ inxi -bM
System:Host: localhost.localdomain Kernel: 4.19.0-0.rc2.git2.1.fc30.x86_64
x86_64 bits: 64
Desktop: Gnome 3.30.0 Distro: Fedora release 29 (Rawhide)
Machine: Type:
https://bugzilla.kernel.org/show_bug.cgi?id=49431
mario.vuke...@dantian.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|--
Hi all.
When working on the DRM driver for Atmel LCDC the first approach
was to use a MFD driver, that had two sub-drivers:
- PWM dirver
- DRM driver
Feedback was that the PWM feature was too small to warrant a MFD driver.
(There was no consencus on this, but I anyway went ahead).
So the new app
On Sat, Sep 8, 2018 at 10:17 PM, Sam Ravnborg wrote:
> Hi all.
>
> When working on the DRM driver for Atmel LCDC the first approach
> was to use a MFD driver, that had two sub-drivers:
> - PWM dirver
> - DRM driver
>
> Feedback was that the PWM feature was too small to warrant a MFD driver.
> (The
> >
> > So the open question is how to fix this dependency challenge?
> >
> > 1) Drop the generic backlight driver and implement all pwm/backlight
> >handling in the driver.
> > 2) Re-introduce the MFD driver.
> > 3) ?
> >
> > Any good ideas?
>
> component.c should be able to cope. The driver
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #11 from Jon (jon...@gmail.com) ---
Still frequent freezing. Two so far today, one time everything froze but audio
from youtube in firefox continued to play. Numlock light frozen on keyboard,
no input would work from mouse, etc, but
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #20 from Sylvain BERTRAND ---
Found the bug, very probably.
It seems to be an upstream bug: a 32bits multiplication overflow on TSC
frequency introduced in recent TSC cleanup:
---
Found the bug, very probably.
It seems to be an upstream bug: a 32bits multiplication overflow on TSC
frequency introduced in recent TSC cleanup:
commit cf7a63ef4e0203f6f33284c69e8188d91422de83
Author: Pavel Tatashin
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #21 from Dmitrii Tcvetkov ---
(In reply to Sylvain BERTRAND from comment #20)
> Roughly, if you have a cpu with a frequency above 4.2GHz (max unsigned
> 32bits),
> linux time subsystem gets broken leading to the timeouts in displaypo
https://bugzilla.kernel.org/show_bug.cgi?id=200621
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
45 matches
Mail list logo
