2012/10/18 Eunchul Kim :
> Hi All.
>
> I am responsible for a display part from Samsung Electronics
> Telecommunication Division.
> and I am going to add post-processing features in exynos drm.
> If you have some opinion of this patch,
> please give some comments about my patch.
>
> IPP is stands
n Selection' on
function '@main'
I am using llvm 3.1 on HD4890.
--
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/20121026/faa6b82b/attachment.html>
If an entity has sink pads, at least one of them must be connected to
another pad with an enabled link. If a driver with multiple sink pads has
more strict requirements the check should be done in the driver itself.
Just requiring one sink pad is connected with an enabled link is enough
API-wise:
https://bugs.freedesktop.org/show_bug.cgi?id=56139
--- Comment #6 from Alexandre Demers ---
(In reply to comment #5)
> Created attachment 69113 [details] [review]
> possible fix
>
> (In reply to comment #4)
> > the bug appeared. So it seems blanking the display controllers with for(i =
> > 0; i
On Thursday 25 of October 2012 20:06:54 Heinz Diehl wrote:
> On 25.10.2012, Pawe? Sikora wrote:
>
> > what is the reason of loading nouveau driver for laptops
> > with nvidia optimus and enabling vga switcheroo
> > which doesn't work in such (optimus) cases.
>
> You can safely compile a kernel
attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121026/061f8522/attachment.html>
0 are split. It is not a linear history.
--
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/20121026/eefbd1d8/attachment.html>
When I restart my display manager (GDM) from tty0, I get a corrupted
image where parts of the X display before I restarted GDM become visible
on both the newly started X server instance as on tty0. When moving the
mouse in X, the current (correct) image around the cursor is replaced by
the imag
.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121026/5066e9b7/attachment.html>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121026/15c09c73/attachment.html>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121026/3de3245d/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121026/f7ff4a15/attachment.html>
|unspecified |git
--
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/20121026/6a739bee/attachment.html>
se:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121026/4e28a9df/attachment.html>
Hi Thierry,
Thank you for the patch, and sorry for the late reply.
On Monday 15 October 2012 20:03:42 Thierry Reding wrote:
> Platform device drivers usually use the driver-private data for their
> own purposes. Having it overwritten by drm_platform_init() is confusing
> and error-prone.
If you
https://bugs.freedesktop.org/show_bug.cgi?id=56437
--- Comment #2 from Andy Furniss ---
I saw this yesterday after rebuilding Mesa and running nexuiz.
Running again worked without error.
This is the second time I've seen it, the first was a couple of weeks ago,
again after a rebuild of mesa this
http://lists.freedesktop.org/archives/dri-devel/attachments/20121026/729bd063/attachment.html>
On 10/26/2012 01:05 AM, Daniel Vetter wrote:
On Fri, Oct 26, 2012 at 6:43 AM, Justin P. Mattock
wrote:
No worries, it is another ILK hang similar to the ones reported earlier
- it just seems the ring stops advancing. Hopefully it is a missing w/a
from http://cgit.freedesktop.org/~danvet/drm/lo
On 10/26/2012 01:05 AM, Daniel Vetter wrote:
> On Fri, Oct 26, 2012 at 6:43 AM, Justin P. Mattock
> wrote:
>>>
>>> No worries, it is another ILK hang similar to the ones reported earlier
>>> - it just seems the ring stops advancing. Hopefully it is a missing w/a
>>> from http://cgit.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #6 from Alex Deucher ---
You can just checkout a commit on master around the time 8.0 was branched.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel
On Thursday 25 of October 2012 20:06:54 Heinz Diehl wrote:
> On 25.10.2012, Paweł Sikora wrote:
>
> > what is the reason of loading nouveau driver for laptops
> > with nvidia optimus and enabling vga switcheroo
> > which doesn't work in such (optimus) cases.
>
> You can safely compile a kernel
https://bugzilla.kernel.org/show_bug.cgi?id=49531
--- Comment #6 from Igor Murzov 2012-10-26 12:22:10 ---
Created an attachment (id=84961)
--> (https://bugzilla.kernel.org/attachment.cgi?id=84961)
full dmesg output for v3.7.0-rc2+
The kernel is not from the origin/master, it's the drm-fixe
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #5 from mdrs...@t-online.de ---
And the bug still exists when using the top of the
master branch:
b78b62497f1e5cc64eb924c64e4685fe5d814fd7
I'm not so sure what commits I should start the bisecting with since
8.0 and 9.0 are split.
When I restart my display manager (GDM) from tty0, I get a corrupted
image where parts of the X display before I restarted GDM become visible
on both the newly started X server instance as on tty0. When moving the
mouse in X, the current (correct) image around the cursor is replaced by
the imag
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #4 from mdrs...@t-online.de ---
The dmesg and xorg log files are done with the top of the 9.0 branch
5fe5aa8e55a8db0b80f6ff9838bad47ce0406fd0
--
You are receiving this mail because:
You are the assignee for the bug.
_
From: Yuly Novikov
Signed-off-by: Yuly Novikov
[Jani: ripped this change separate from the scaling mode change support]
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/intel_dp.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/dr
From: Yuly Novikov
LVDS allowed changing panel fitting scaling mode, while eDP didn't. Copied
relevant code from LVDS to eDP.
Signed-off-by: Yuly Novikov
[Jani: use fitting mode in intel_panel, remove default mode change]
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/intel_dp.c | 31 +
Prepare for supporting scaling mode configuration also in eDP.
Includes a drive-by-removal of an outdated comment about fitting mode.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/intel_drv.h |1 +
drivers/gpu/drm/i915/intel_lvds.c | 24 ++--
2 files changed, 11
[Dropped lkml, added intel-gfx]
Hi Yuly, here's a slightly modified version of your patch, rebased on
drm-intel-next-queued. I kept your authorship, but any new errors are
totally mine...
These are compile tested only; I'd appreciate if you could check it
still does what it says on the box!
BR,
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #3 from mdrs...@t-online.de ---
Created attachment 69133
--> https://bugs.freedesktop.org/attachment.cgi?id=69133&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #2 from mdrs...@t-online.de ---
Created attachment 69132
--> https://bugs.freedesktop.org/attachment.cgi?id=69132&action=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
_
Hi
2012/10/26 Jani Nikula :
> [Dropped lkml, added intel-gfx]
>
> Hi Yuly, here's a slightly modified version of your patch, rebased on
> drm-intel-next-queued. I kept your authorship, but any new errors are
> totally mine...
>
> These are compile tested only; I'd appreciate if you could check it
https://bugs.freedesktop.org/show_bug.cgi?id=56437
--- Comment #1 from maxi...@free.fr ---
I was unclear about LLVM:
I am using the llvm glsl backend when I trigger this error.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freedesktop.org/show_bug.cgi?id=56437
maxi...@free.fr changed:
What|Removed |Added
OS|All |Linux (All)
Version|unspecif
https://bugs.freedesktop.org/show_bug.cgi?id=56437
Priority: medium
Bug ID: 56437
Assignee: dri-devel@lists.freedesktop.org
Summary: LLVM ERROR: Cannot select: target intrinsic
%llvm.AMDIL.mad when running Heaven
Severity: no
On 10/26/2012 01:05 AM, Daniel Vetter wrote:
On Fri, Oct 26, 2012 at 6:43 AM, Justin P. Mattock
wrote:
No worries, it is another ILK hang similar to the ones reported earlier
- it just seems the ring stops advancing. Hopefully it is a missing w/a
from http://cgit.freedesktop.org/~danvet/drm/lo
On 10/26/2012 01:05 AM, Daniel Vetter wrote:
> On Fri, Oct 26, 2012 at 6:43 AM, Justin P. Mattock
> wrote:
>>>
>>> No worries, it is another ILK hang similar to the ones reported earlier
>>> - it just seems the ring stops advancing. Hopefully it is a missing w/a
>>> from http://cgit.freedesktop.or
Hi,
On 10/25/2012 11:27 PM, Ilija Hadzic wrote:
>
> Can you give the attached patch a whirl and let me know if it fixes
> the problem?
>
> As I indicated in my previous note, vmwgfx should be the only affected
> driver because it looks at dev_mapping in the open hook (others do it
> when they c
On Fri, Oct 26, 2012 at 6:43 AM, Justin P. Mattock
wrote:
>>
>> No worries, it is another ILK hang similar to the ones reported earlier
>> - it just seems the ring stops advancing. Hopefully it is a missing w/a
>> from http://cgit.freedesktop.org/~danvet/drm/log/?h=ilk-wa-pile
>> -Chris
>>
>
> wel
We check whether this pointer is NULL a few lines later in the function
so probably we should check here too.
Signed-off-by: Dan Carpenter
---
This is a static checker fix.
diff --git a/drivers/gpu/drm/drm_lock.c b/drivers/gpu/drm/drm_lock.c
index d752c96..036253e 100644
--- a/drivers/gpu/drm/dr
Hi Tomasz,
On Wed, Oct 10, 2012 at 7:46 AM, Tomasz Stanislawski
wrote:
> This patch introduces usage of dma_map_sg to map memory behind
> a userspace pointer to a device as dma-contiguous mapping.
>
Perhaps I'm missing something, but I don't understand the purpose of
this patch. If the device ca
below is quick review.
2012/10/18 Eunchul Kim :
> IPP stand for Image Post Processing and supports image scaler/rotator
> /crop/flip/csc(color space conversion) and input/output DMA operations using
> ipp drivers.
> also supports writeback and display output operations.
> ipp driver include FIMC,
https://bugzilla.kernel.org/show_bug.cgi?id=49531
--- Comment #5 from Michel D?nzer 2012-10-26 08:21:53
---
Please attach the full dmesg output showing the drm/radeon initialization
messages.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receivi
On Fri, 26 Oct 2012, Thomas Hellstrom wrote:
> Hi,
>
> On 10/25/2012 11:27 PM, Ilija Hadzic wrote:
>>
>> Can you give the attached patch a whirl and let me know if it fixes the
>> problem?
>>
>> As I indicated in my previous note, vmwgfx should be the only affected
>> driver because it looks
2012/10/18 Eunchul Kim :
> Hi All.
>
> I am responsible for a display part from Samsung Electronics
> Telecommunication Division.
> and I am going to add post-processing features in exynos drm.
> If you have some opinion of this patch,
> please give some comments about my patch.
>
> IPP is stands
> Unlikely as most of the code I've written belongs to Intel or Red Hat. I
> also have better things to do with life than sue Nvidia and start an all
> out copyright and patent war in Linuxspace.
I forgot to ask, but after your petty G+ trolling, if most of the code
belings to Intel or Red Hat, wh
https://bugs.freedesktop.org/show_bug.cgi?id=56139
Alex Deucher changed:
What|Removed |Added
Attachment #68760|0 |1
is obsolete|
Hi Thierry,
Thank you for the patch, and sorry for the late reply.
On Monday 15 October 2012 20:03:42 Thierry Reding wrote:
> Platform device drivers usually use the driver-private data for their
> own purposes. Having it overwritten by drm_platform_init() is confusing
> and error-prone.
If you
Hi
2012/10/26 Jani Nikula :
> [Dropped lkml, added intel-gfx]
>
> Hi Yuly, here's a slightly modified version of your patch, rebased on
> drm-intel-next-queued. I kept your authorship, but any new errors are
> totally mine...
>
> These are compile tested only; I'd appreciate if you could check it
From: Yuly Novikov
Signed-off-by: Yuly Novikov
[Jani: ripped this change separate from the scaling mode change support]
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/intel_dp.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/dr
From: Yuly Novikov
LVDS allowed changing panel fitting scaling mode, while eDP didn't. Copied
relevant code from LVDS to eDP.
Signed-off-by: Yuly Novikov
[Jani: use fitting mode in intel_panel, remove default mode change]
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/intel_dp.c | 31 +
Prepare for supporting scaling mode configuration also in eDP.
Includes a drive-by-removal of an outdated comment about fitting mode.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/intel_drv.h |1 +
drivers/gpu/drm/i915/intel_lvds.c | 24 ++--
2 files changed, 11
[Dropped lkml, added intel-gfx]
Hi Yuly, here's a slightly modified version of your patch, rebased on
drm-intel-next-queued. I kept your authorship, but any new errors are
totally mine...
These are compile tested only; I'd appreciate if you could check it
still does what it says on the box!
BR,
On Fri, 26 Oct 2012, Thomas Hellstrom wrote:
Hi,
On 10/25/2012 11:27 PM, Ilija Hadzic wrote:
Can you give the attached patch a whirl and let me know if it fixes the
problem?
As I indicated in my previous note, vmwgfx should be the only affected
driver because it looks at dev_mapping in
https://bugzilla.kernel.org/show_bug.cgi?id=49531
--- Comment #6 from Igor Murzov 2012-10-26 12:22:10 ---
Created an attachment (id=84961)
--> (https://bugzilla.kernel.org/attachment.cgi?id=84961)
full dmesg output for v3.7.0-rc2+
The kernel is not from the origin/master, it's the drm-fixe
_CRTC_CONTROL.
Could this be a clue?
--
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/20121026/4c6d325c/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=49531
--- Comment #5 from Michel Dänzer 2012-10-26 08:21:53 ---
Please attach the full dmesg output showing the drm/radeon initialization
messages.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receivin
Hi,
On 10/25/2012 11:27 PM, Ilija Hadzic wrote:
Can you give the attached patch a whirl and let me know if it fixes
the problem?
As I indicated in my previous note, vmwgfx should be the only affected
driver because it looks at dev_mapping in the open hook (others do it
when they create an
On Fri, Oct 26, 2012 at 6:43 AM, Justin P. Mattock
wrote:
>>
>> No worries, it is another ILK hang similar to the ones reported earlier
>> - it just seems the ring stops advancing. Hopefully it is a missing w/a
>> from http://cgit.freedesktop.org/~danvet/drm/log/?h=ilk-wa-pile
>> -Chris
>>
>
> wel
We check whether this pointer is NULL a few lines later in the function
so probably we should check here too.
Signed-off-by: Dan Carpenter
---
This is a static checker fix.
diff --git a/drivers/gpu/drm/drm_lock.c b/drivers/gpu/drm/drm_lock.c
index d752c96..036253e 100644
--- a/drivers/gpu/drm/dr
Hi Linus,
Just radeon fixes in this one,
some new PCI IDs,
ATPX regression fix,
async VM regression fixes
some module options fixes.
Dave.
The following changes since commit b8e902f24fdd16c4373ddc37a4e150c4afe9c6db:
drm/ttm: Fix a theoretical race in ttm_bo_cleanup_refs() (2012-10-23 10:15:2
Dave Airlie writes:
> On Thu, Oct 25, 2012 at 3:07 AM, Alex Deucher
> wrote:
> > On Wed, Oct 24, 2012 at 12:33 PM, Egbert Eich wrote:
> >> The Radeon driver reduces the framebuffer resolution to 8bpp if
> >> a device with less than 32 Mb VRAM is found. This causes the
> >> framebuffer to r
On 10/25/2012 01:47 AM, Chris Wilson wrote:
On Thu, 25 Oct 2012 10:16:08 +0200, Daniel Vetter wrote:
On Thu, Oct 25, 2012 at 7:22 AM, Justin P. Mattock
wrote:
here is a link to the file..: intel_error_decode
http://www.filefactory.com/file/22bypyjhs4mx
I haven't figured out how to access t
63 matches
Mail list logo
