it happens when changing image contents directly with loadimage only.
then the software cursor is overdrawn and on mouse move it restores
the previous content below the cursor.
--
cinap
---BeginMessage---
So, I finally got tired of slow desktop switching with the nvidia
driver and thought I'd
I didn't seem to see any improvement after applying the mtrr patch...
did you make any changes to the vganvidia file before compiling? I
haven't looked at the 'pat' thing, I'll have to check that out.
for the pat business, i did:
/n/sources/plan9//sys/src/9/pc/vganvidia.c:371,377 -
On Tue, Jul 14, 2009 at 5:06 AM, erik quanstromquans...@quanstro.net wrote:
I didn't seem to see any improvement after applying the mtrr patch...
did you make any changes to the vganvidia file before compiling? I
haven't looked at the 'pat' thing, I'll have to check that out.
for the pat
I believe I properly applied the pat patch, but I'm not really seeing
any improvement. At least, it still takes fully two seconds to bring
one large window in front of another.
that's because the screen is not double-buffered. pat or mtrr do
not improve reads from video memory. there is no
On Tue, Jul 14, 2009 at 9:10 AM, erik quanstromquans...@coraid.com wrote:
I believe I properly applied the pat patch, but I'm not really seeing
any improvement. At least, it still takes fully two seconds to bring
one large window in front of another.
that's because the screen is not
As I'm reading it, the change to vganvidia.c you posted above
(re-pasted below) does pat stuff. Am I confused? I don't think pat and
mtrr are the same thing...
they're not. mtrr operates at the physical address level and
it's just a bunch of registers that control caching of a (limited set
So, I finally got tired of slow desktop switching with the nvidia
driver and thought I'd give vesa another shot. However, upon
rebooting with vesa in 1600x1200x16 mode, I'm seeing strange artifacts
when using vncv and fgb's equis; an example from vnc is shown at
On Mon Jul 13 19:58:54 EDT 2009, j...@csplan9.rit.edu wrote:
So, I finally got tired of slow desktop switching with the nvidia
driver and thought I'd give vesa another shot.
i have had trouble with vesa cursor in 1600x1200. generally when
i have trouble, the cursor won't move at all. one
I'm finding that vesa works nicely on
my terminal in terms of speed, and I'm not seeing any difference in 16
bit vs. 32 bit color.
VESA has stopped being useful on my SiS 55x, flash based workstation.
The symptoms are an insistence that the video inputs are incorrect
(the monitor complains).
On Mon, Jul 13, 2009 at 7:42 PM, erik quanstromquans...@quanstro.net wrote:
On Mon Jul 13 19:58:54 EDT 2009, j...@csplan9.rit.edu wrote:
So, I finally got tired of slow desktop switching with the nvidia
driver and thought I'd give vesa another shot.
i have had trouble with vesa cursor in
10 matches
Mail list logo
