From: Jon Smirl <jonsmirl@yahoo.com>
To: fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Large framebuffers and HIGHMEM systems
Date: Tue, 9 Sep 2003 14:28:24 -0700 (PDT) [thread overview]
Message-ID: <20030909212824.95374.qmail@web14916.mail.yahoo.com> (raw)
Fbdev needs to come up with a general solution for mapping large framebuffers
on systems with over 1GB memory. For example my system does not have 64MB of
free address space below 1GB, this causes my framebuffer drivers to fail when
loading. With RAM prices at $200 for 1GB memory 1GB systems will be common
during the 2.6 timeframe.
There are many possible solutions...
1) add reserve=XXXX to the kernel at boot. Drawback to this is reserving
256-512MB takes this memory out of lowmem kernel use. This will push page
tables into highmem slowing the whole system down.
2) Only map a 2048x2048x32 piece of the framebuffer. This still uses 16MB of
address space which may not always be available. It could be possible to modify
the kernel to always reserve this much address space at boot.
3) Only map what is actually needed on each mode change. Mode change could fail
at run time if not enough free address space.
4) Map the buffer into the highmem address space using the highmem access
macros.
5) Map the fb in a user process and send it signals to draw.
I would also suggest modifying all current fb drivers to print a message about
adding reserve=xxxxx at boot if their ioremap() of the fb fails. This will at
least point people at an immediate work around.
=====
Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2003-09-09 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 21:28 Jon Smirl [this message]
2003-09-10 8:40 ` Large framebuffers and HIGHMEM systems Geert Uytterhoeven
2003-09-10 15:01 ` Jon Smirl
2003-09-10 15:56 ` Sven Luther
2003-09-10 16:21 ` Geert Uytterhoeven
2003-09-10 16:33 ` Sven Luther
2003-09-12 22:56 ` James Simmons
2003-09-13 3:19 ` Jon Smirl
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=20030909212824.95374.qmail@web14916.mail.yahoo.com \
--to=jonsmirl@yahoo.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 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).