* VESA framebuffer changes in 2.4
@ 2001-02-06 1:37 Joel Beach
0 siblings, 0 replies; only message in thread
From: Joel Beach @ 2001-02-06 1:37 UTC (permalink / raw)
To: linux-kernel
Just wondering whether the VESA framebuffer underwent wholesale changes
between 2.2 and 2.4. I use a graphical console (1024x768 @ 8bit colour
depth), and full-screen scrolling performance is *really* bad. When I type
'ls' in a directory with a large amount of files, it becomes really slow.
Under 2.2.18 I have no such problems.
I run my 2.4.1 system in a separate partition, built from scratch, and the
only important difference I can imagine between my 2.2.18 and 2.4.1 configs
is that I use agetty rather than mingetty in 2.4.1.
I can make my scrolling performance in 2.4.1 very good by appending the
following option in lilo.conf:
video=vesa:ywrap,mtrr
This makes scrolling down very fast - as fast if not faster than 2.2.18 -
but scrolling up one line at a time is absolutely horrendous - it seems to
redraw the whole screen. It is easy to test this bu using vi to edit a
file. I know this is probably due to the way that ywrap uses the video
card's memory as a buffer for scrolling down, but why is the behaviour so
different from 2.2.18?
BTW, I use an nvidia GeForce DDR 32MB RAM. I don't subscribe to the list,
so please CC replies to joelbeach@optushome.com.au
Thanks,
Joel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-02-06 1:35 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-02-06 1:37 VESA framebuffer changes in 2.4 Joel Beach
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.