LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bernardo Innocenti <bernie@develer.com>
To: Bernardo Innocenti <bernie@develer.com>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	Linux Frame Buffer Device Development 
	<linux-fbdev-devel@lists.sourceforge.net>,
	lkml <linux-kernel@vger.kernel.org>, aleph <aleph@develer.com>
Subject: Re: [Linux-fbdev-devel] How to mmap a shadow framebuffer in virtual memory
Date: Tue, 06 Feb 2007 15:57:31 +0100	[thread overview]
Message-ID: <45C8975B.30508@develer.com> (raw)
In-Reply-To: <45AB196B.7090409@develer.com>

Bernardo Innocenti wrote:

> I still couldn't solve my problem, but thanks for helping.
> 
> The way you map memory in ps3fb_mmap() is basically the same.
> In my case, memory is allocated with __get_free_pages() instead
> of being at an absolute physical address, but I can't see how
> it could make any difference.

A few weeks ago I found the solution, which I report here to help
people who are googling for the same problem.

consistent_alloc() performed all the required magic to allocate
a contiguous buffer in phisical memory:

 -       if (!(fb_info.shadow = (void *)__get_free_pages(GFP_KERNEL, OLED_MEMORDER))
 +       if (!(fb_info.shadow = consistent_alloc(GFP_KERNEL, PAGE_ALIGN(OLED_MEMSIZE),
 +                       &fb_info.shadow_phys, PTE_BUFFERABLE))


The complete patch set is here, just in case:

   http://www.develer.com/patches/linux/pending/

-- 
   // Bernardo Innocenti - Develer S.r.l., R&D dept.
 \X/  http://www.develer.com/


      reply	other threads:[~2007-02-06 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14  0:24 Bernardo Innocenti
2007-01-14 11:13 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2007-01-15  6:04   ` Bernardo Innocenti
2007-02-06 14:57     ` Bernardo Innocenti [this message]

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=45C8975B.30508@develer.com \
    --to=bernie@develer.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=aleph@develer.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [Linux-fbdev-devel] How to mmap a shadow framebuffer in virtual memory' \
    /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

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).