Re: [9fans] image/memimage speed

["Aki Nyrhinen" <anyrhine@gmail.com>]

On Mon, Dec 8, 2008 at 1:22 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> 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?

actually, i'm using a hack very similar to the vgavesa stuff above,
except for vganvidia, precisely for the reasons you mention (all of them),
plus the fact that acceleration is broken for my current nvidia card and i
could not care less.

the changes are just as trivial (and the same code can be used).
the reason why i didn't originally post the mtrr hack with all vga
drivers changed was that while the added buffering makes performance
much more constant, it is a loss for non-obscured foreground windows
for things like 'time du -a /usr', due to losing hwfill and hwscroll.