From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] image/memimage speed
Date: Sun, 7 Dec 2008 18:22:15 -0500 [thread overview]
Message-ID: <8a42fc9d59a7901b46b1d47db88610ba@quanstro.net> (raw)
In-Reply-To: <218917ef0812070900u4f15e817nf78f2b99e83ebc75@mail.gmail.com>
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
next prev parent reply other threads:[~2008-12-07 23:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 22:00 Iruata Souza
2008-11-30 23:54 ` Iruata Souza
2008-12-01 1:29 ` erik quanstrom
2008-12-01 1:54 ` andrey mirtchovski
2008-12-01 2:35 ` erik quanstrom
2008-12-01 3:30 ` andrey mirtchovski
2008-12-01 6:41 ` Paul Lalonde
2008-12-01 14:19 ` Steve Simon
2008-12-01 14:33 ` erik quanstrom
2008-12-05 6:39 ` ron minnich
2008-12-05 13:35 ` erik quanstrom
2008-12-05 18:27 ` Russ Cox
2008-12-05 18:32 ` Russ Cox
2008-12-05 18:49 ` ron minnich
2008-12-05 19:21 ` Paul Lalonde
2008-12-05 19:25 ` erik quanstrom
2008-12-05 19:30 ` Paul Lalonde
2008-12-05 19:40 ` erik quanstrom
2008-12-05 20:11 ` ron minnich
2008-12-06 5:52 ` Paul Lalonde
2008-12-07 17:00 ` Aki Nyrhinen
2008-12-07 23:22 ` erik quanstrom [this message]
2008-12-08 0:17 ` Aki Nyrhinen
2008-12-01 15:24 plalonde
2008-12-05 5:22 ` sqweek
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=8a42fc9d59a7901b46b1d47db88610ba@quanstro.net \
--to=quanstro@quanstro.net \
--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).