Right now hdmiphy operations and configs are kept inside hdmi driver. hdmiphy
related code is tightly coupled with hdmi ip driver. Physicaly they are
different devices and should be instantiated independently.
In terms of versions/mapping/configurations Hdmi and hdmiphy are independent
of each oth
Right now hdmiphy operations and configs are kept inside hdmi driver. hdmiphy
related code is tightly coupled with hdmi ip driver. Physicaly they are
different devices and should be instantiated independently.
In terms of versions/mapping/configurations Hdmi and hdmiphy are independent
of each oth
Exynos hdmi driver is using drm_display_mode for setting timing values
for a supported resolution. Conversion to fb_videomode and then comparing
with the mixer/hdmi/phy limits is not required. Instead, drm_display_mode
fields cane be directly compared.
v2:
1) Removed convert_to_video_timing().
2)
Include definitions of used types by including drm/drm.h
Sparse output:
/usr/include/drm/tegra_drm.h:21:
found __[us]{8,16,32,64} type without
#include
Signed-off-by: Emil Goode
---
include/uapi/drm/tegra_drm.h |2 ++
1 file changed, 2 insertions(+)
diff --git a/include/ua
On 04/26/2013 09:42 PM, Tomasz Figa wrote:
On Friday 26 of April 2013 11:48:50 Sylwester Nawrocki wrote:
On 04/26/2013 10:20 AM, Inki Dae wrote:
Exactly right. it's my mistake. But now it seems that
__mode_of_device_table is multi defined at fimd and g2d side so there
still is module build erro
https://bugs.freedesktop.org/show_bug.cgi?id=63997
Priority: medium
Bug ID: 63997
Assignee: dri-devel@lists.freedesktop.org
Summary: Artifacts on the screen using a HD7480D on a A4-5300
APU
Severity: normal
Classification
https://bugs.freedesktop.org/show_bug.cgi?id=63997
Mirko changed:
What|Removed |Added
Summary|Artifacts on the screen |Artifacts using a HD7480D
|usi
https://bugzilla.kernel.org/show_bug.cgi?id=57201
Summary: [vgaswitcheroo] increased consumption and hangups
after hibernating with disabled radeon
Product: Drivers
Version: 2.5
Kernel Version: 3.9-rc8-24-gd7d7271
Platform: All
https://bugzilla.kernel.org/show_bug.cgi?id=57201
--- Comment #1 from Nikolay Amiantov 2013-04-27 14:03:36
---
Created an attachment (id=100111)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100111)
dmesg with failure from 3.9-rc8
--
Configure bugmail: https://bugzilla.kernel.org/us
https://bugzilla.kernel.org/show_bug.cgi?id=57201
--- Comment #2 from Nikolay Amiantov 2013-04-27 14:05:32
---
Created an attachment (id=100121)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100121)
dmesg after rebooting from failure, 3.9-rc8
Also, after rebooting (with magic-sysrq),
https://bugzilla.kernel.org/show_bug.cgi?id=57201
--- Comment #3 from Nikolay Amiantov 2013-04-27 14:06:26
---
Created an attachment (id=100131)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100131)
dmesg, 3.8.8
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=ema
https://bugzilla.kernel.org/show_bug.cgi?id=57201
Nikolay Amiantov changed:
What|Removed |Added
Attachment #100101|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=63632
Andy Furniss changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=62959
--- Comment #61 from Alexandre Demers ---
I compiled drm-next yesterday (which should be found in kernel 3.10 any day
now). I've been able to run piglit r600.test without any problem 2 times (just
in case, I rebooted beween each). Is there any th
https://bugs.freedesktop.org/show_bug.cgi?id=62959
--- Comment #62 from Alexandre Demers ---
(In reply to comment #60)
> The first bisect kernel I try gives me youtube videos that are blocks of
> gibberish. What to do about that?
>
> 3.7.1. crashed like previous kernels (showing text boot screen
https://bugs.freedesktop.org/show_bug.cgi?id=62959
--- Comment #63 from udo ---
Currently running 3.6.0-02886-gd9a8074 and that one help up OK so far for 28
hours. How long to continue before declaring this kernel good?
Previous bisect kernel 3.6.0-05487-g24d7b40 was found within 24 hours to have
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #64 from Alexandre Demers ---
Any of the patchs pushed in drm-next? I've been playing with drm-next since
yesterday and display is running fine when setting GRUB_GFXPAYLOAD_LINUX=keep
at GRUB's launch.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=57567
--- Comment #65 from Alex Deucher ---
(In reply to comment #64)
> Any of the patchs pushed in drm-next? I've been playing with drm-next since
> yesterday and display is running fine when setting
> GRUB_GFXPAYLOAD_LINUX=keep at GRUB's launch.
Yes
https://bugs.freedesktop.org/show_bug.cgi?id=63997
--- Comment #1 from Alex Deucher ---
Please attach your xorg log and dmesg output and a picture of the corruption.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-dev
https://bugs.freedesktop.org/show_bug.cgi?id=63979
--- Comment #4 from Alex Deucher ---
Grab Dave's drm-next tree:
http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-next
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=63997
--- Comment #2 from Mirko ---
Created attachment 78561
--> https://bugs.freedesktop.org/attachment.cgi?id=78561&action=edit
Artefacts video
This is the video with glxgears running
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=63997
--- Comment #3 from Mirko ---
Created attachment 78562
--> https://bugs.freedesktop.org/attachment.cgi?id=78562&action=edit
Xorg log
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=63997
--- Comment #4 from Mirko ---
Created attachment 78563
--> https://bugs.freedesktop.org/attachment.cgi?id=78563&action=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=63865
--- Comment #7 from Hieu Hoang ---
Created attachment 78569
--> https://bugs.freedesktop.org/attachment.cgi?id=78569&action=edit
dmesg of patched kernel
With the patch, my monitor goes in to stand by right after modesetting (the
power LED is e
ou are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130427/6bfc2c07/attachment.html>
part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130427/e267a459/attachment-0001.html>
acts on the screen but very low performance
(glxgear get about 4 fps).
Glamor is disabled.
--
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/20130427/5ecc1a93/attachment.html>
vel/attachments/20130427/bd1e3a73/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=57201
Summary: [vgaswitcheroo] increased consumption and hangups
after hibernating with disabled radeon
Product: Drivers
Version: 2.5
Kernel Version: 3.9-rc8-24-gd7d7271
Platform: All
https://bugzilla.kernel.org/show_bug.cgi?id=57201
--- Comment #1 from Nikolay Amiantov 2013-04-27
14:03:36 ---
Created an attachment (id=100111)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100111)
dmesg with failure from 3.9-rc8
--
Configure bugmail: https://bugzilla.kernel.org/us
https://bugzilla.kernel.org/show_bug.cgi?id=57201
--- Comment #2 from Nikolay Amiantov 2013-04-27
14:05:32 ---
Created an attachment (id=100121)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100121)
dmesg after rebooting from failure, 3.9-rc8
Also, after rebooting (with magic-sysrq),
https://bugzilla.kernel.org/show_bug.cgi?id=57201
--- Comment #3 from Nikolay Amiantov 2013-04-27
14:06:26 ---
Created an attachment (id=100131)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100131)
dmesg, 3.8.8
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=ema
https://bugzilla.kernel.org/show_bug.cgi?id=57201
Nikolay Amiantov changed:
What|Removed |Added
Attachment #100101|application/octet-stream|text/plain
mime type|
org/archives/dri-devel/attachments/20130427/1f28f15c/attachment.html>
e any thing pushed in there that is
expected to help?
--
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/20130427/956b19ed/attachment.html>
t you see in between in case they are not linked to
the same bug.
--
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/20130427/117199c0/attachment.html>
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20130427/79d4e203/attachment-0001.html>
iving 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/20130427/a2acfbdb/attachment.html>
GRUB's launch.
Yes.
--
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/20130427/12bdaf07/attachment.html>
attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130427/7941620a/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130427/a1c46332/attachment.html>
ssignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130427/bf0cadf9/attachment.html>
xt part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130427/e748894e/attachment.html>
xt part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130427/b19418fe/attachment.html>
Hi Thierry,
I don't know this code well but the drm/drm.h has an #if def so that
either linux/types.h is included or the __[us]* types are defined in
a different way with the comment "One of the BSDs".
Also I sent a patch last year to include linux/types.h in exynos_drm.h
but it now includes drm/d
45 matches
Mail list logo
