On Mon, Sep 24, 2018 at 08:13:08PM +0300, Ville Syrjälä wrote:
> On Mon, Sep 24, 2018 at 06:10:14PM +0200, Daniel Vetter wrote:
> > On Thu, Sep 20, 2018 at 09:51:43PM +0300, Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > Read the HDMI infoframes from the hbuf and unpack them into
> >
On Mon, Sep 24, 2018 at 07:36:08PM +0300, Ville Syrjälä wrote:
> On Mon, Sep 24, 2018 at 05:51:16PM +0200, Daniel Vetter wrote:
> > On Thu, Sep 20, 2018 at 09:51:38PM +0300, Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > We want to start tracking which infoframes are enabled, so let's
On Fri, Sep 28, 2018 at 06:30:35PM +0300, Laurent Pinchart wrote:
> Hi Souptick,
>
> On Friday, 28 September 2018 18:05:18 EEST Laurent Pinchart wrote:
> > On Thursday, 27 September 2018 09:34:18 EEST Souptick Joarder wrote:
> > > On Tue, Sep 18, 2018 at 10:05 PM Souptick Joarder wrote:
> > >> con
https://bugs.freedesktop.org/show_bug.cgi?id=107991
kyle.de...@mykolab.com changed:
What|Removed |Added
Component|Drivers/Gallium/radeonsi|Other
QA Contact|dri-de
https://bugs.freedesktop.org/show_bug.cgi?id=107991
kyle.de...@mykolab.com changed:
What|Removed |Added
Summary|RX580 ~ ring gfx timeout ~ |RX580 ~ ring gfx timeout ~
Hi Dave,
Just one fixup patch to avoid Exynos DRM driver from being broken
with enhancement patch series of IOMMU framework[1].
This patch just makes it reuse default IOMMU domain instead of
allocating a fake one.
Ps. We'd like to push this one to help enhancing the IOMMU and
https://bugs.freedesktop.org/show_bug.cgi?id=107991
--- Comment #6 from Rob Stolarz ---
I get the same crash (drm amdgpu ring gfx timeout) on an RX 480 in The Legend
of Zelda: Twilight Princess (GameCube) with any combination of Arch's linux and
linux-git packages, regular Mesa packages+vulkan-ra
On Tue, Sep 25, 2018 at 06:06:11PM +0200, Thierry Reding wrote:
> From: Thierry Reding
>
> If an I2C adapter doesn't match the provided device tree node, also try
> matching the parent's device tree node. This allows finding an adapter
> based on the device node of the parent device that was used
https://bugs.freedesktop.org/show_bug.cgi?id=108107
--- Comment #1 from mikhail.v.gavri...@gmail.com ---
Created attachment 141816
--> https://bugs.freedesktop.org/attachment.cgi?id=141816&action=edit
monitor photo
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=108107
Bug ID: 108107
Summary: The GPU Vega 56 randomly hang while I playing in the
"Injustice: Gods Among Us Ultimate Edition" game under
steam play
Product: DRI
Versi
https://bugs.freedesktop.org/show_bug.cgi?id=108099
Jan Vesely changed:
What|Removed |Added
Resolution|--- |NOTOURBUG
Blocks|
Hi Sergey,
> Sergey Suloev hat am 30. September 2018 um 15:24
> geschrieben:
>
>
> Here is my log
>
> [ 2.868157] [drm:drm_setup_crtcs [drm_kms_helper]] connector 29
> enabled? yes
> [ 2.868199] [drm:drm_setup_crtcs [drm_kms_helper]] connector 44
> enabled? no
> [ 2.868234] [drm:dr
Hi, Emil,
On 09/05/2018 03:53 PM, Emil Velikov wrote:
On 5 September 2018 at 14:20, Thomas Hellstrom wrote:
In that case, please give me 24h to do a libdrm release before pushing.
I had to push some workarounds for the sandboxing mentioned earlier :-\
Thanks
Emil
Ouch, I just pushed the pa
Den 30.09.2018 15.24, skrev Sergey Suloev:
Here is my log
[ 2.868157] [drm:drm_setup_crtcs [drm_kms_helper]] connector 29
enabled? yes
[ 2.868199] [drm:drm_setup_crtcs [drm_kms_helper]] connector 44
enabled? no
[ 2.868234] [drm:drm_setup_crtcs [drm_kms_helper]] connector 50
enabled?
https://bugzilla.kernel.org/show_bug.cgi?id=201275
--- Comment #7 from quirin.blae...@freenet.de ---
For now i have resolved this problem by simply removing patch for 4.18.11
git diff
93b100ddda3be284be160e9ccba28c7f8f21ab73^1..93b100ddda3be284be160e9ccba28c7f8f21ab73
and patch -R -p1
or without
https://bugs.freedesktop.org/show_bug.cgi?id=108096
--- Comment #8 from Dieter Nützel ---
(In reply to Dieter Nützel from comment #6)
> Created attachment 141792 [details]
> dmesg-4.19.0-rc1-1.g7262353-default+.log-25.09
Hi,
could this be a hint?
[6.716492] [drm] Fence fallback timer expire
Den 29.09.2018 22.52, skrev Sergey Suloev:
Hi,
the last error message seems to come from the following config option:
CONFIG_DRM_FBDEV_OVERALLOC=200
Changing it to the default value fixes the issue:
CONFIG_DRM_FBDEV_OVERALLOC=100
If you enable drm debug (drm.debug=0xff), you get some more
On Wed, Sep 26, 2018 at 02:06:50PM +0200, Thomas Zimmermann wrote:
> This patch unifies the naming of DRM functions for reference counting
> of struct drm_device. The resulting code is more aligned with the rest
> of the Linux kernel interfaces.
>
> Signed-off-by: Thomas Zimmermann
> Acked-by: Sh
18 matches
Mail list logo