From: Walt H <waltabbyh@comcast.net>
To: Antonino Daplas <adaplas@pol.net>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: vesafb problem with 1GB Ram and possible fix
Date: Sun, 30 Mar 2003 15:16:29 -0800 [thread overview]
Message-ID: <3E877ACD.2070002@comcast.net> (raw)
In-Reply-To: <1048973887.1014.16.camel@localhost.localdomain>
Antonino Daplas wrote:
> True, vesafb does not support mode changes. However, the extra graphics
> memory is useful for some framebuffer-based applications that implement
> multi-buffering. DirectFB, for instance, takes advantage of this since
> it uses a frontbuffer and a backbuffer (display the frontbuffer, render
> to the backbuffer, swap the front and backbuffer pointers, then display
> the new frontbuffer). Xine and mplayer using the framebuffer backend
> are probably using similar setups.
>
> Tony
>
>
Thanks for the info Tony. Sounds like my setup wouldn't be ideal for
mass consumption. I don't use vesafb for anything other than the
graphical console with large number of columns and rows, so it shouldn't
affect me. I just needed a quick hack for a fix since I got a new MP
system with lots 'o ram and no penguins :( It's all good now though..
-Walt
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
prev parent reply other threads:[~2003-03-30 23:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 16:41 vesafb problem Walt H
2003-03-27 19:02 ` Jurriaan
2003-03-27 19:34 ` Walt H
2003-03-27 21:39 ` Bongani Hlope
2003-03-27 22:30 ` Walt H
2003-03-28 3:55 ` Bongani Hlope
2003-03-27 22:27 ` Walt H
2003-03-27 23:11 ` Walt H
2003-03-28 20:59 ` vesafb problem with 1GB Ram and possible fix Walt H
2003-03-29 10:41 ` Antonino Daplas
2003-03-29 20:24 ` Walt H
2003-03-29 21:39 ` Antonino Daplas
2003-03-30 23:16 ` Walt H [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=3E877ACD.2070002@comcast.net \
--to=waltabbyh@comcast.net \
--cc=adaplas@pol.net \
--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.