linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hunold@linuxtv.org (Michael Hunold)
To: linux-arm-kernel@lists.infradead.org
Subject: dma_alloc_writecombine() and MAX_ORDER
Date: Tue, 03 May 2011 08:25:32 +0200	[thread overview]
Message-ID: <4DBF9FDC.6080400@linuxtv.org> (raw)
In-Reply-To: <20110429142755.GS5126@n2100.arm.linux.org.uk>

Hello Russell,

on 04/29/2011 04:27 PM Russell King - ARM Linux said the following:
> On Fri, Apr 29, 2011 at 02:50:37PM +0200, Michael Hunold wrote:

>> Now I have a new panel with a higher resolution and more bits-per-pixel.
>> I want to use double-buffering with DirectFB and so my framebuffer size
>> exceeds 4Mb.

> You could try this patch.  It steals the memory for the coherent and
> writecombine memory at boot time, so MAX_ORDER no longer comes into the
> problem.  You may need to define CONSISTENT_WC_SIZE and CONSISTENT_DMA_SIZE
> appropriately to gain sufficient memory.  Note that the sum of those two
> must be a multiple of 2MB, and individually must be a multiple of 1MB.

I really want to try this patch out, but unfortunately, I don't know to
which tree I can apply it to. :-(

I'm working on a tree which is based on vanilla 2.6.38 and has the
additions for the platform I'm working with, but there the patch won't
apply cleanly.

The tree can be found here
http://git.labs.kernelconcepts.de/?p=topas.git;a=summary

So I thought I should try "devel-stable" from
http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm.git
but there are even more rejects there.

Can you please tell me from which tree you created this patch?

Best regards
Michael.

  reply	other threads:[~2011-05-03  6:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 12:50 dma_alloc_writecombine() and MAX_ORDER Michael Hunold
2011-04-29 14:27 ` Russell King - ARM Linux
2011-05-03  6:25   ` Michael Hunold [this message]
2011-05-03  8:44     ` Russell King - ARM Linux

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=4DBF9FDC.6080400@linuxtv.org \
    --to=hunold@linuxtv.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).