Exynos drm driver cannot support DRIVER_HAVE_IRQ feature because it uses
driver specific one instead of routine of drm framework to
install/uninstall irq handler.
Signed-off-by: Joonyoung Shim
---
Changelog from v1:
- Keep below code
drm_dev->irq_enabled = true;
drivers/gpu/drm/exynos/
re receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140412/0a7a20de/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #30 from Tom Yan ---
Created attachment 131971
--> https://bugzilla.kernel.org/attachment.cgi?id=131971&action=edit
vbios
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #31 from Tom Yan ---
(In reply to Alex Deucher from comment #29)
> Can you also try the attached patch which reverses the hpd polarity?
Unfortunately the patch doesn't work (with or without the dp-specific code).
Maybe you should tr
iled
make: *** [all-recursive] Error 1
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140412/4075ff7e/attachment.html>
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20140412/5a9d39f7/attachment-0001.html>
...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140412/8ed1c5a4/attachment.html>
|---
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140412/04eb55ea/attachment.html>
built.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140412/f00ed3d9/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=68571
--- Comment #37 from kilobug at kilobug.org ---
I changed my motherboard and CPU today (went from Intel to AMD CPU), but it
didn't change the issue at all. I still get a freeze very quickly when playing
a HD video on mplayer with the "GL" video out
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #11 from sdh ---
Nopes. It makes the UVD errors go away, but the boot still gets stuck at the
same point. Everything hangs up, requiring me to do a hard reboot.
Weirdly, I could not find any errors in either syslog or Xorg, which make
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #12 from Christian K?nig ---
(In reply to sdh from comment #11)
> Nopes. It makes the UVD errors go away, but the boot still gets stuck at the
> same point. Everything hangs up, requiring me to do a hard reboot.
Well that the UVD erro
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #13 from sdh ---
Can you suggest me a good way to debug this and read the logs? Everything hangs
up, so I do a hard reboot and start with nomodeset parameter to see the logs.
Is there a better way to do this?
--
You are receiving thi
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #14 from Christian K?nig ---
(In reply to sdh from comment #13)
> Can you suggest me a good way to debug this and read the logs? Everything
> hangs up, so I do a hard reboot and start with nomodeset parameter to see
> the logs. Is ther
Hi,
I've been seeing the following warning when a mode is attempted to be
set after boot when no display connectors are connected. This typically
happens if your platform has just a HDMI output, and the TV connected
to the HDMI output is fully powered off.
This has been happening for quite some
tp://lists.freedesktop.org/archives/dri-devel/attachments/20140412/2fea7e6d/attachment.html>
part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140412/f32894ea/attachment.html>
Hi Andrzej,
Thanks for your contributions.
2014-04-11 23:11 GMT+09:00 Andrzej Hajda :
> Hi Inki,
>
> This patchset refactors drm device initialization. Details are described
> in respective patches. It is an alternative to DT supernode concept.
>
> The first patch uses linker sections to get rid
On Fri, Apr 11, 2014 at 5:35 PM, Daniel Vetter
wrote:
> Dave accidentally merged the wrong version of the patch in
>
> commit fd3c02531461924853db65f2664db361b53a70d3
> Author: Daniel Vetter
> Date: Wed Dec 11 11:34:26 2013 +0100
>
> drm/omap: call drm_put_dev directly in ->remove
>
> whic
---
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140412/499fd12f/attachment.html>
Does someone have an idea on how to deal with this issue?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140412/36e3b770/attachment-0001.html>
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #15 from sdh ---
Thanks, that helped :)
Doing a 'modprobe radeon' after booting up gives the following errors:
radeon :01:00.0: GPU lockup CP stall for more than 1msec
radeon :01:00.0: GPU lockup (waiting for 0x000
https://bugzilla.kernel.org/show_bug.cgi?id=73901
Bug ID: 73901
Summary: Kernel crash after modprobe radeon runpm=1
Product: Drivers
Version: 2.5
Kernel Version: 3.14
Hardware: x86-64
OS: Linux
Tree: Mainline
https://bugzilla.kernel.org/show_bug.cgi?id=73901
--- Comment #1 from Pali Roh?r ---
Created attachment 131981
--> https://bugzilla.kernel.org/attachment.cgi?id=131981&action=edit
syslog output
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73901
Pali Roh?r changed:
What|Removed |Added
Attachment #131981|application/octet-stream|text/plain
mime type|
On Sat, Apr 12, 2014 at 12:32 PM, Russell King - ARM Linux
wrote:
>
> I've been seeing the following warning when a mode is attempted to be
> set after boot when no display connectors are connected. This typically
> happens if your platform has just a HDMI output, and the TV connected
> to the HD
On Sat, Apr 12, 2014 at 10:42:52PM +0200, Daniel Vetter wrote:
> On Sat, Apr 12, 2014 at 12:32 PM, Russell King - ARM Linux
> wrote:
> >
> > I've been seeing the following warning when a mode is attempted to be
> > set after boot when no display connectors are connected. This typically
> > happen
On Sat, Apr 12, 2014 at 11:20 PM, Russell King - ARM Linux
wrote:
> So what happens is that a mode is attempted to be set with no connectors.
That case is the other nonsense use of ->set_config I've curbed with
all the fb helper fixes.
BUG_ON(set->fb && set->num_connectors == 0);
in drm_crt
On Sat, Apr 12, 2014 at 11:49:44PM +0200, Daniel Vetter wrote:
> On Sat, Apr 12, 2014 at 11:20 PM, Russell King - ARM Linux
> wrote:
> > So what happens is that a mode is attempted to be set with no connectors.
>
> That case is the other nonsense use of ->set_config I've curbed with
> all the fb
29 matches
Mail list logo
