This patch removes property error handling. because property couldn't be NULL.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c | 12
drivers/gpu/drm/exynos/exynos_drm_gsc.c | 12
drivers/gpu/drm/exynos/exynos_drm_ipp.c |5 -
3 files
Hi All.
This patch fix some issue and cleanup code.
please check my commit and let me know about your comment.
Changelog v3:
- Subject clean like bellow:
* change all subject name from Inki.Dae
Changelog v2:
- This patch set fixes the following:
* consider both case of vflip and hflip: we use
This patch change current command name from cmd to c_node.
because we are using the member name, 'cmd', for command control ioctl in
another structure.
so, this patch changes it to c_node to avoid such confusing.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c|8
This patch considers both case of vflip and hflip.
If we want that the contents in buffer to be rotated to 180 degree,
then we can use h,vflip or 180 degree.
Changelog v2:
- added EXYNOS_DRM_FLIP_BOTH enum value to avoid build warnning.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exyn
This patch fixes erroneous register read.
reall function needs register base address + offset but
exynos_drm_gsc module used only offset to read a register.
so this patch uses gsc_read function instead of readl.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exynos_drm_gsc.c |2 +-
1
This patch cleanup corrects some comments to abbreviation.
We would like to prevent it stands misunderstood.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c |2 +-
drivers/gpu/drm/exynos/exynos_drm_gsc.c |2 +-
drivers/gpu/drm/exynos/exynos_drm_ipp.c |2 +-
From: JoongMock Shin
This patch removes color bar pattern register because we don't use the register
anymore.
because it doesn't support color bar feature for writeback operation.
camera driver only supports color bar feature. but IPP doesn't support camera
driver.
Signed-off-by: JoongMock Shi
From: Jinyoung Jeon
This patch fixes incorrect interrupt induced by m2m operation.
the m2m operation calls s/w reset every frame but there is the case that
the interrupt to m2m operation occures after s/w reset sometimes.
So this patch makes dma and capture operations stop at s/w reset
to avoid i
This patch removes needless parenthesis.
This was pointed out but in case of fimc side. we missed it.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimc.c
b/driv
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Florian Mickler changed:
What|Removed |Added
CC||flor...@mickler.org
--- Comment #51 fr
https://bugs.freedesktop.org/show_bug.cgi?id=58166
Florian Mickler changed:
What|Removed |Added
CC||flor...@mickler.org
--- Comment #9 fro
https://bugs.freedesktop.org/show_bug.cgi?id=58272
Florian Mickler changed:
What|Removed |Added
CC||flor...@mickler.org
--- Comment #11 fr
On Fri, 2012-12-21 at 13:39 +0200, Terje Bergstrom wrote:
> diff --git a/include/trace/events/host1x.h b/include/trace/events/host1x.h
> index d98d74c..e087910 100644
> --- a/include/trace/events/host1x.h
> +++ b/include/trace/events/host1x.h
> @@ -37,6 +37,214 @@ DECLARE_EVENT_CLASS(host1x,
>
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #12 from Alex Deucher ---
Make sure your kernel has this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=0953e76e91f4b6206cef50bd680696dc6bf1ef99
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=58655
Priority: medium
Bug ID: 58655
Assignee: dri-devel@lists.freedesktop.org
Summary: Screen totally corrupted on CAYMAN
Severity: blocker
Classification: Unclassified
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=58372
--- Comment #9 from Alexandre Demers ---
(In reply to comment #8)
> (In reply to comment #7)
> > Created attachment 71883 [details]
> > dmesg with drm-fixes-3.8
> >
> > The dmesg message changed after merging in drm-fixes-3.8:
> >
> > [drm:ever
https://bugs.freedesktop.org/show_bug.cgi?id=58656
Priority: medium
Bug ID: 58656
Assignee: dri-devel@lists.freedesktop.org
Summary: [drm : evergreen_vm_reg_valid] *ERROR* Invalid
register 0x8040 in CS
Severity: major
Cla
https://bugs.freedesktop.org/show_bug.cgi?id=58656
--- Comment #1 from Alexandre Demers ---
@commit a585b8f3a6681d1138ed1a33ed4c3195a53c2a73
Make IsVertexArray...
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=58656
Alexandre Demers changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=58655
Alexandre Demers changed:
What|Removed |Added
CC||alexandre.f.dem...@gmail.co
https://bugs.freedesktop.org/show_bug.cgi?id=58655
Alexandre Demers changed:
What|Removed |Added
Summary|Screen totally corrupted on |Screen totally corrupted on
https://bugs.freedesktop.org/show_bug.cgi?id=58655
--- Comment #2 from Alex Deucher ---
Mesa hadn't previously emitted that register for cayman so the kernel wasn't
expecting it. Fixed with this patch:
http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3.8&id=668bbc81baf0f34df832d8aca5
https://bugs.freedesktop.org/show_bug.cgi?id=58655
Thomas Rohloff changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=58658
Priority: medium
Bug ID: 58658
Assignee: dri-devel@lists.freedesktop.org
Summary: Minecraft menu broken on CAYMAN
Severity: normal
Classification: Unclassified
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=58658
--- Comment #1 from Thomas Rohloff ---
Sorry for the wrong mime-type. The screenshot is image/png, not text/plain.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-dev
https://bugs.freedesktop.org/show_bug.cgi?id=58658
Thomas Rohloff changed:
What|Removed |Added
Attachment #71997|text/plain |image/png
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=58659
Priority: medium
Bug ID: 58659
Assignee: dri-devel@lists.freedesktop.org
Summary: With latest kernel 3.8-rc1, compiz crashes after boot
Severity: normal
Classification: Unclassified
https://bugs.freedesktop.org/show_bug.cgi?id=58660
Priority: medium
Bug ID: 58660
Assignee: dri-devel@lists.freedesktop.org
Summary: Radeon HD 6950 completely broken.
Severity: normal
Classification: Unclassified
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=58660
--- Comment #1 from Thomas Rohloff ---
Forget to say: This is on newest mesa from git with kernel 3.8-rc1 (+ this
patch:
http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3.8&id=668bbc81baf0f34df832d8aca5c7d5e19a493c68
)
--
You are r
https://bugs.freedesktop.org/show_bug.cgi?id=58661
Priority: medium
Bug ID: 58661
Assignee: dri-devel@lists.freedesktop.org
Summary: Chat text and other things flashing in Minecraft on
CAYMAN
Severity: normal
Classificati
https://bugs.freedesktop.org/show_bug.cgi?id=58661
--- Comment #1 from Thomas Rohloff ---
As it is to large for a attachment here a link to a video showing the issue:
https://www.dropbox.com/s/981hzit2ittwgyz/out-85.ogv
--
You are receiving this mail because:
You are the assignee for the bug.
_
Hi Alex,
got the sickest bug on 3.8-rc1, see below. The GPU locks up somewhere
down radeon_fence_wait_seq, judging by the error messages.
And this doesn't happen with 3.7, of course.
Let me know if you need any more info, thanks.
[16273.668350] radeon :02:00.0: GPU lockup CP stall for more
Hello, Alex!
Thank you for your reply!
Quoting Alex Deucher :
That patch only affects SI chips which yours is not, so it's probably
not what's causing problems for you.
OK, maybe. Bisection can lead to a wrong commit if the problem is not
100% reproducible.
This looks like a duplicate
On 12/13/2012 09:31 PM, Bjorn Helgaas wrote:
[+cc Betty]
On Thu, Dec 13, 2012 at 4:04 PM, Lucas Kannebley Tavares
wrote:
On architectures such as ppc64, there is no root bus device (it belongs
to the hypervisor). DRM attempted to get one, causing a null-pointer
dereference.
In addition to p
During the process of obtaining the speed cap for the device, it
attempts go get the PCI Host bus. However on architectures such as PPC
or IA64, those do not appear as devices.
Signed-off-by: Lucas Kannebley Tavares
---
drivers/gpu/drm/drm_pci.c |5 +
1 files changed, 5 insertions(+), 0
Replacing these calls avoids compatibility problems with PCIe v1/v2
Capability structures.
Signed-off-by: Lucas Kannebley Tavares
---
drivers/gpu/drm/drm_pci.c |8 ++--
1 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/drm_pci.c b/drivers/gpu/drm/drm_pci.c
i
Hi!
I've noticed a regression using 3.7 on my Thinkpad X300.
In Cinnamon and in KDE with Desktop Effects, all graphics are slow and
studdering. Moving a window results in about 5 frames per second.
glxgears achieves about 14 fps, versus ~60 in unaffected kernels.
X is from Debian unstable:
https://bugs.freedesktop.org/show_bug.cgi?id=58272
--- Comment #13 from Andy Furniss ---
(In reply to comment #12)
> Make sure your kernel has this patch:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;
> h=0953e76e91f4b6206cef50bd680696dc6bf1ef99
I tested drm-next h
https://bugs.freedesktop.org/show_bug.cgi?id=58166
Andy Furniss changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=58372
--- Comment #10 from Serkan Hosca ---
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > Created attachment 71883 [details]
> > > dmesg with drm-fixes-3.8
> > >
> > > The dmesg message changed after merging in
https://bugs.freedesktop.org/show_bug.cgi?id=58658
--- Comment #2 from Alex Deucher ---
I suspect this is a mesa 3D driver issue rather than a kernel issue. Was this
working in the past? Can you bisect?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=58659
--- Comment #1 from Alex Deucher ---
Make sure your kernel has this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=0953e76e91f4b6206cef50bd680696dc6bf1ef99
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=58666
Priority: medium
Bug ID: 58666
Assignee: dri-devel@lists.freedesktop.org
Summary: rv670 + llvm = errors.
Severity: normal
Classification: Unclassified
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=58660
Alex Deucher changed:
What|Removed |Added
Summary|Radeon HD 6950 completely |Radeon HD 6950 completely
https://bugs.freedesktop.org/show_bug.cgi?id=58661
--- Comment #2 from Alex Deucher ---
I suspect this is a mesa 3D driver issue rather than a kernel issue. Was this
working in the past? Can you bisect?
--
You are receiving this mail because:
You are the assignee for the bug.
On Sat, Dec 22, 2012 at 3:35 PM, Borislav Petkov wrote:
> Hi Alex,
>
> got the sickest bug on 3.8-rc1, see below. The GPU locks up somewhere
> down radeon_fence_wait_seq, judging by the error messages.
>
> And this doesn't happen with 3.7, of course.
>
> Let me know if you need any more info, than
https://bugs.freedesktop.org/show_bug.cgi?id=58667
Priority: medium
Bug ID: 58667
Assignee: dri-devel@lists.freedesktop.org
Summary: Random crashes on CAYMAN
Severity: normal
Classification: Unclassified
OS: All
Rep
https://bugs.freedesktop.org/show_bug.cgi?id=58667
--- Comment #1 from Thomas Rohloff ---
Created attachment 72006
--> https://bugs.freedesktop.org/attachment.cgi?id=72006&action=edit
Full dmesg output
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freedesktop.org/show_bug.cgi?id=58667
--- Comment #2 from Alex Deucher ---
Is this a regression? Does it happen with older versions of mesa or kernel?
If it's a regression can you identify which component (mesa or kernel) and
bisect?
--
You are receiving this mail because:
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=58354
--- Comment #3 from Alex Deucher ---
Can you get the dmesg output when the lockup happens?
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-deve
https://bugs.freedesktop.org/show_bug.cgi?id=58667
--- Comment #3 from Alex Deucher ---
May also be related to bug 58354.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.
https://bugs.freedesktop.org/show_bug.cgi?id=58660
--- Comment #3 from Thomas Rohloff ---
The thing is that I can't access dmesg after the crash. Not even SysMagRQ
works.
See my dmesg with the other BIOS here:
https://bugs.freedesktop.org/attachment.cgi?id=72006
I have the BIOSes still lying ar
https://bugs.freedesktop.org/show_bug.cgi?id=58660
--- Comment #4 from Thomas Rohloff ---
Created attachment 72008
--> https://bugs.freedesktop.org/attachment.cgi?id=72008&action=edit
BIOS 0 (locked shaders)
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=58660
--- Comment #5 from Thomas Rohloff ---
Created attachment 72009
--> https://bugs.freedesktop.org/attachment.cgi?id=72009&action=edit
BIOS 1 (unlocked shaders)
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freedesktop.org/show_bug.cgi?id=58658
--- Comment #3 from Thomas Rohloff ---
I'm not sure if it's mesa or kernel. Yes, it was working before last update
(updated mesa + kernel).
I might be able to bisect later but atm my time is limited and as I don't even
know what to bisect (kerne
On Sat, Dec 22, 2012 at 07:01:31PM -0500, Alex Deucher wrote:
> What chip is this?
I think it is RV635. Here's the whole 3.8-rc1 dmesg.
[0.00] Linux version 3.8.0-rc1 (boris@liondog) (gcc version 4.7.2
(Debian 4.7.2-4) ) #13 SMP PREEMPT Sat Dec 22 11:48:54 CET 2012
[0.00] Command
https://bugs.freedesktop.org/show_bug.cgi?id=58661
--- Comment #3 from Thomas Rohloff ---
I'm not sure if it's mesa or kernel. Yes, it was working before last update
(updated mesa + kernel).
I might be able to bisect later but atm my time is limited and as I don't even
know what to bisect (kerne
https://bugs.freedesktop.org/show_bug.cgi?id=58661
--- Comment #4 from Thomas Rohloff ---
Also I'm not sure about the dmesg output from here:
https://bugs.freedesktop.org/show_bug.cgi?id=58667 - It might be connected.
--
You are receiving this mail because:
You are the assignee for the bug.
___
On Sat, Dec 22, 2012 at 7:25 PM, Borislav Petkov wrote:
> On Sat, Dec 22, 2012 at 07:01:31PM -0500, Alex Deucher wrote:
>> What chip is this?
>
> I think it is RV635. Here's the whole 3.8-rc1 dmesg.
Does booting with radeon.wb=0 help?
Alex
___
dri-deve
https://bugs.freedesktop.org/show_bug.cgi?id=58354
--- Comment #4 from Alexandre Demers ---
Hitting some other bug right now with bug 58655. I'll apply the proposed patch
for the other bug and I'll see what I get then.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=58667
--- Comment #4 from Thomas Rohloff ---
!Is this a regression? Does it happen with older versions of mesa or kernel?!
Not that I know about.
"May also be related to bug 58354."
Do you have the path noted there ("drm/radeon: use DMA engine for VM
https://bugs.freedesktop.org/show_bug.cgi?id=58667
--- Comment #5 from Thomas Rohloff ---
I should really read before I click save, sorry. Here again:
"Is this a regression? Does it happen with older versions of mesa or kernel?"
Not that I know about.
"May also be related to bug 58354."
Do you
On Mon, Dec 17, 2012 at 5:25 PM, Markus Trippelsdorf
wrote:
> On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
>> On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
>> wrote:
>> > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
>> >> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
>> >>
https://bugs.freedesktop.org/show_bug.cgi?id=58354
--- Comment #5 from Alex Deucher ---
Created attachment 72013
--> https://bugs.freedesktop.org/attachment.cgi?id=72013&action=edit
possible fix
Does this patch fix the issue?
--
You are receiving this mail because:
You are the assignee for t
From: Alex Deucher
CP changes:
- make sure the new VM base address hits the registers
- wait for the VM invalidate to finish
DMA changes:
- wait for the VM invalidate to finish
May fix:
https://bugs.freedesktop.org/show_bug.cgi?id=58354
https://bugs.freedesktop.org/show_bug.cgi?id=58667
possibly
From: Alex Deucher
CP changes:
- make sure the new VM base address hits the registers
- wait for the VM invalidate to finish
DMA changes:
- wait for the VM invalidate to finish
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/si.c | 41 +
driver
https://bugs.freedesktop.org/show_bug.cgi?id=58354
--- Comment #6 from Alexandre Demers ---
Created attachment 72014
--> https://bugs.freedesktop.org/attachment.cgi?id=72014&action=edit
dmesg after lockup
This is the salvaged dmesg retrieved with the help of a ssh connection. Sadly,
I don't th
https://bugs.freedesktop.org/show_bug.cgi?id=58354
--- Comment #7 from Alexandre Demers ---
Would it help if I was increasing the debug level?
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-dev
https://bugs.freedesktop.org/show_bug.cgi?id=58354
--- Comment #8 from Alexandre Demers ---
(In reply to comment #5)
> Created attachment 72013 [details] [review]
> possible fix
>
> Does this patch fix the issue?
Testing right away.
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=58354
--- Comment #9 from Alexandre Demers ---
Doesn't fix it, it locks as before. Sadly, dmesg seems to loose the count
because of another bug introduced in 3.8-rc1. Now that I moved to 3.8-rc1,
there is a huge amount of messages appearing in errors.l
https://bugs.freedesktop.org/show_bug.cgi?id=58354
--- Comment #10 from Alexandre Demers ---
(In reply to comment #9)
> Doesn't fix it, it locks as before. Sadly, dmesg seems to loose the count
> because of another bug introduced in 3.8-rc1. Now that I moved to 3.8-rc1,
> there is a huge amount o
> *drm_dev,
> --
> 1.7.4.1
>
> ___
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
-- next part ------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121222/8531f5f4/attachment.html>
o haven't been updated
correctly. Definitely this was our mistakes.
Thanks,
Inki Dae
> Other questions I'll look at later - in particular
> - I don't see how the work queue is locked against the main thread of
> execution within the driver
> - There is a general DRI question here about HDC
On 21/12/2012 13:04, Ozan ?a?layan wrote:
>> Of course it is, but why would you disable automatic fan management?
>>
>> You are supposed to activate it and let it activated at all time.
> It's not me but someone inexperienced playing with sysfs tunables for example
> :)
Ah, sure. Well, there is d
vel/attachments/20121222/4ae14ff2/attachment.html>
Thank's for your advice.
Your opinion is very helpful to me.
I will consider your comments, and then I resend it.
Thank's
BR
Eunchul Kim
On 12/21/2012 08:53 PM, Alan Cox wrote:
> On Fri, 21 Dec 2012 18:47:57 +0900
> Eunchul Kim wrote:
>
>> HDCP stands for High-bandwidth Digital Content Protecti
On 21.12.2012 16:36, Thierry Reding wrote:
> On Fri, Dec 21, 2012 at 01:39:21PM +0200, Terje Bergstrom wrote:
>> +static struct platform_driver tegra_drm_platform_driver = {
>> +.driver = {
>> +.name = "tegradrm",
>
> This should be "tegra-drm" to match the module name.
We've actu
Dear Sean Paul.
Thank's for your comment.
I am in charge of Display Part in Samsung TN.
and I also use exynos drm and I contributed some part to dri-devel(e.g
IPPs).
Your comment is very helpful to me.
I answer to your comment. please check my answer.
Thank's
BR
Eunchul Kim
On 12/22/2012 04:2
This patch removes property error handling. because property couldn't be NULL.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c | 12
drivers/gpu/drm/exynos/exynos_drm_gsc.c | 12
drivers/gpu/drm/exynos/exynos_drm_ipp.c |5 -
3 files
Hi All.
This patch fix some issue and cleanup code.
please check my commit and let me know about your comment.
Changelog v3:
- Subject clean like bellow:
* change all subject name from Inki.Dae
Changelog v2:
- This patch set fixes the following:
* consider both case of vflip and hflip: we use
This patch change current command name from cmd to c_node.
because we are using the member name, 'cmd', for command control ioctl in
another structure.
so, this patch changes it to c_node to avoid such confusing.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c|8
This patch considers both case of vflip and hflip.
If we want that the contents in buffer to be rotated to 180 degree,
then we can use h,vflip or 180 degree.
Changelog v2:
- added EXYNOS_DRM_FLIP_BOTH enum value to avoid build warnning.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exyn
This patch fixes erroneous register read.
reall function needs register base address + offset but
exynos_drm_gsc module used only offset to read a register.
so this patch uses gsc_read function instead of readl.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exynos_drm_gsc.c |2 +-
1
This patch cleanup corrects some comments to abbreviation.
We would like to prevent it stands misunderstood.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c |2 +-
drivers/gpu/drm/exynos/exynos_drm_gsc.c |2 +-
drivers/gpu/drm/exynos/exynos_drm_ipp.c |2 +-
From: JoongMock Shin
This patch removes color bar pattern register because we don't use the register
anymore.
because it doesn't support color bar feature for writeback operation.
camera driver only supports color bar feature. but IPP doesn't support camera
driver.
Signed-off-by: JoongMock Shi
From: Jinyoung Jeon
This patch fixes incorrect interrupt induced by m2m operation.
the m2m operation calls s/w reset every frame but there is the case that
the interrupt to m2m operation occures after s/w reset sometimes.
So this patch makes dma and capture operations stop at s/w reset
to avoid i
This patch removes needless parenthesis.
This was pointed out but in case of fimc side. we missed it.
Signed-off-by: Eunchul Kim
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimc.c
b/driv
because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121222/ea0fee5a/attachment-0001.html>
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/20121222/0e18fd82/attachment.html>
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/20121222/1b3f4be0/attachment.html>
the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121222/8efb5727/attachment.html>
- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121222/eaa673cc/attachment.html>
6aaac3ef656aebc8bc20cd27a
Opening it, I'm hitting 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/20121222/32abf593/attachment-0001.html>
ri-devel/attachments/20121222/5e76a80b/attachment.html>
attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121222/071ad1b7/attachment.html>
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20121222/5a26aa77/attachment.html>
...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121222/eb683c17/attachment.html>
because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121222/5782c190/attachment.html>
xes-3.8&id=668bbc81baf0f34df832d8aca5c7d5e19a493c68
Which should show up in 3.8 and stable soon.
--
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/
ves/dri-devel/attachments/20121222/173d62b7/attachment.html>
1 - 100 of 127 matches
Mail list logo
