From: Ivajlo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: minchan@kernel.org, pavel@ucw.cz, sre@debian.org,
pali.rohar@gmail.com, pc+n900@asdf.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: OMAPFB: CMA allocation failures
Date: Fri, 06 Dec 2013 10:31:11 +0200 [thread overview]
Message-ID: <52A18B4F.1070809@gmail.com> (raw)
In-Reply-To: <52A062A0.3070005@ti.com>
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 requests it.
>
YAY!!! That one seems to fix the issue.
Though I had to revert 7faa92339bbb1e6b9a80983b206642517327eb75 (well, I
hacked check_horiz_timing_omap3 to always return 0). Otherwise I have
"omapdss DISPC error: horizontal timing too tight" error when try to
play anything above 320x240 or so. I'll look at the issue.
Regards,
Ivo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-12-06 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1847426616.52843.1383681351015.JavaMail.apache@mail83.abv.bg>
2013-11-30 10:00 ` OMAPFB: CMA allocation failures Ivajlo Dimitrov
2013-12-05 11:25 ` Tomi Valkeinen
2013-12-06 8:31 ` Ivajlo Dimitrov [this message]
2013-11-05 19:55 Ивайло Димитров
-- strict thread matches above, loose matches on Subject: below --
2013-10-29 12:47 Ивайло Димитров
2013-10-30 5:53 ` Minchan Kim
2013-10-30 12:19 ` Tomi Valkeinen
2013-10-23 21:59 Ивайло Димитров
2013-10-24 7:00 ` Tomi Valkeinen
2013-10-16 6:33 Ивайло Димитров
2013-10-15 6:49 Ивайло Димитров
2013-10-15 7:36 ` Tomi Valkeinen
2013-10-28 7:37 ` Minchan Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A18B4F.1070809@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=pc+n900@asdf.org \
--cc=sre@debian.org \
--cc=tomi.valkeinen@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).