All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Shivappa Kushtagi <kushtagi@gmail.com>
Subject: Re: Re: Virtual framebuffer driver - mmap problem
Date: Thu, 9 Sep 2004 18:16:51 +0800	[thread overview]
Message-ID: <200409091816.51541.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0409091029190.10508@waterleaf.sonytel.be>

On Thursday 09 September 2004 16:31, Geert Uytterhoeven wrote:
> >
> > So if PAGE_SIZE is 4096, to allocate 8192 bytes, use order = 1. Note that
> > there is an upper limit to order, so keep videomemorysize small.
>
> And the upper limit is 128 kiB on most platforms. Hence even 640x480 in 8
> bpp won't fit...
>
> Probably you can make a fb_mmap() hook that's compatible with the
> vmalloc()'ed frame buffer and thus doesn't suffer from this limitation, but
> it will require more code and more knowledge of memory management
> internals.
>

Actually, I discovered that MAX_ORDER in 2.4 is 10 (4MiB) and 11 in 2.6 
(8MiB), so it's probably not as limiting as it seems. However, the 
probability of __get_free_pages() failing at such a high order is very high.

Tony




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click

      reply	other threads:[~2004-09-09 10:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08 13:51 Virtual framebuffer driver - mmap problem Shivappa Kushtagi
2004-09-09  0:31 ` Antonino A. Daplas
2004-09-09  8:31   ` Geert Uytterhoeven
2004-09-09 10:16     ` Antonino A. Daplas [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=200409091816.51541.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=geert@linux-m68k.org \
    --cc=kushtagi@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.