From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ugliness in vesa
Date: Mon, 13 Jul 2009 22:23:30 -0700 [thread overview]
Message-ID: <7d3530220907132223o58711065w5a669c7fd0084e53@mail.gmail.com> (raw)
In-Reply-To: <005081991c9166ef69f3305f12a04fac@quanstro.net>
On Mon, Jul 13, 2009 at 7:42 PM, erik quanstrom<quanstro@quanstro.net> wrote:
> On Mon Jul 13 19:58:54 EDT 2009, john@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 problem i
> did not finish looking at were the spill-over bits in vga register 13.
>
> nvidia is slow, but have you tried with the newly-integrated mtrr or
> the pat stuff? my pentium iv terminal is pretty snappy in 1600x1200x32 + pat
> my amd terminal with a pcie card + pat is even snapper, until the screen is read.
> one of these days i'll figure out why the radeon driver is broken for me and/or
> integrate aki's double buffer. even with WT memory, that only speeds the
> write path.
>
> - erik
>
>
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.
John
--
"I've tried programming Ruby on Rails, following TechCrunch in my RSS
reader, and drinking absinthe. It doesn't work. I'm going back to C,
Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba
next prev parent reply other threads:[~2009-07-14 5:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 23:57 john
2009-07-14 2:42 ` erik quanstrom
2009-07-14 5:23 ` John Floren [this message]
2009-07-14 12:06 ` erik quanstrom
2009-07-14 16:03 ` John Floren
2009-07-14 16:10 ` erik quanstrom
2009-07-14 16:23 ` John Floren
2009-07-14 16:49 ` erik quanstrom
2009-07-14 4:42 ` lucio
2009-07-14 6:24 ` cinap_lenrek
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=7d3530220907132223o58711065w5a669c7fd0084e53@mail.gmail.com \
--to=slawmaster@gmail.com \
--cc=9fans@9fans.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).