From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8a42fc9d59a7901b46b1d47db88610ba@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun,  7 Dec 2008 18:22:15 -0500
To: 9fans@9fans.net
In-Reply-To: <218917ef0812070900u4f15e817nf78f2b99e83ebc75@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] image/memimage speed
Topicbox-Message-UUID: 5d5261ee-ead4-11e9-9d60-3106f5b1d025

On Sun Dec  7 12:02:10 EST 2008, anyrhine@gmail.com wrote:
> for vgavesa, you can find this on /n/sources/patch/saved/vesasoftscreen.
> it's been there for a some time.
>
> for all the cards that have support outside the vesa driver, it's probably
> easiest to say monitor=vesa too, since you lose acceleration anyway.
> the related mtrr or the pat patch is good to have with this, or take away
> the mtrr() call from the patch.
>
> i remember we discussed this a few years back, and you were mostly
> concerned about losing accelerated ops then.

sure, but
- what about resolutions higher than vesa specifies,
- what about working with multiple processors
- have you had any luck with vesa on nvidia cards at all?

- erik