On 05.12.2013 13:25, Tomi Valkeinen wrote:
How about the patch below? If I'm not mistaken (and I might) it reserves
separate memory area for omapfb, which is not used by CMA.
If it works, it should be extended to get the parameters via kernel
cmdline, and use that alloc only if the user request
On 2013-11-30 12:00, Ivajlo Dimitrov wrote:
> Ping?
>
> - Original Message - From: "Ивайло Димитров"
> To: "Tomi Valkeinen"
> Cc: ; ; ;
> ; ;
> ;
> Sent: Tuesday, November 05, 2013 9:55 PM
> Subject: Re: OMAPFB: CMA allocation failures
>
Ping?
- Original Message -
From: "Ивайло Димитров"
To: "Tomi Valkeinen"
Cc: ; ; ;
; ; ;
Sent: Tuesday, November 05, 2013 9:55 PM
Subject: Re: OMAPFB: CMA allocation failures
> Оригинално писмо
>От: Tomi Valkeinen
>Относн
> Оригинално писмо
>От: Tomi Valkeinen
>Относно: Re: OMAPFB: CMA allocation failures
>До: Ивайло Димитров
>Изпратено на: Сряда, 2013, Октомври 30 14:19:32 EET
>
>I really dislike the idea of adding the omap vram allocator back. Then
>again,
On 2013-10-29 14:47, Ивайло Димитров wrote:
> However, back to omapfb - my understanding is that the way it uses CMA (in
> its current form) is
> prone to allocation failures way beyond acceptable.
>
> Tomi, what do you think about adding module parameters to allow
> pre-allocating framebuffer
Hello, Ивайло
On Tue, Oct 29, 2013 at 02:47:35PM +0200, Ивайло Димитров wrote:
>
> Hi,
>
>
> > Оригинално писмо
> >От: Minchan Kim
> >Относно: Re: OMAPFB: CMA allocation failures
> >До: Ивайло Димитров
> >Изпратено на:
Hi,
> Оригинално писмо
>От: Minchan Kim
>Относно: Re: OMAPFB: CMA allocation failures
>До: Ивайло Димитров
>Изпратено на: Понеделник, 2013, Октомври 28 09:37:48 EET
>
>
>Hello,
>
>On Tue, Oct 15, 2013 at 09:49:51AM +0300,
Hello,
On Tue, Oct 15, 2013 at 09:49:51AM +0300, Ивайло Димитров wrote:
> Hi
>
> > Оригинално писмо
> >От: Tomi Valkeinen
> >Относно: Re: OMAPFB: CMA allocation failures
> >До: Ивайло Димитров
>
> >Изпратено на: Поне
idea what to look for if I can't reproduce it. The issue is not about
display, but DMA allocation, of which I know very little.
So yes, I suggest you try to discuss this with CMA/DMA people.
Tomi
>
> Regards,
> Ivo
>
> > Оригинално писмо
>
Hi,
I wonder if there is any progress on the issue? Do you need me to send more
data? Or
should I raise the issue with the CMA maintainer?
Regards,
Ivo
> Оригинално писмо
>От: Ивайло Димитров
>Относно: Re: OMAPFB: CMA allocation failures
>До: Tomi Valkeinen
Hi Tomi,
>I think we should somehow find out what the pages are that cannot be
>migrated, and where they come from.
>
>So there are "anonymous pages without mapping" with
>page_count(page) !=
>1. I have to say I don't know what that means =). I need to find some
>time to study the mm.
I
On 15/10/13 09:49, Ивайло Димитров wrote:
> I am using my n900 as a daily/only device since the beginning of 2010, never
> seen such an
> issue with video playback. And as a maintainer of one of the community
> supported kernels for
> n900 (kernel-power) I've never had such an issue reported. O
Hi
> Оригинално писмо
>От: Tomi Valkeinen
>Относно: Re: OMAPFB: CMA allocation failures
>До: Ивайло Димитров
>Изпратено на: Понеделник, 2013, Октомври 14 09:04:35 EEST
>
>
>Hi,
>
>On 12/10/13 17:43, Ивайло Димитров wrote
Hi,
On 12/10/13 17:43, Ивайло Димитров wrote:
> Hi Tomi,
>
> patch
> http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/131269.html
> modifies
> omapfb driver to use DMA API to allocate framebuffer memory instead of
> preallocating VRAM.
>
> With this patch I see a lot of:
>
Hi Tomi,
patch
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-November/131269.html
modifies
omapfb driver to use DMA API to allocate framebuffer memory instead of
preallocating VRAM.
With this patch I see a lot of:
Jan 1 06:33:27 Nokia-N900 kernel: [ 2054.879577] cma:
dma_alloc
15 matches
Mail list logo
