From: Pavel Machek <pavel@suse.cz>
To: Etienne Lorrain <etienne_lorrain@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: specific optimizations for unaccelerated framebuffers
Date: Sat, 6 Oct 2001 00:35:47 +0000 [thread overview]
Message-ID: <20011006003547.A42@toy.ucw.cz> (raw)
In-Reply-To: <3BBC4A4E.AC6106A6@ftel.co.uk> <20011004123118.49603.qmail@web11806.mail.yahoo.com>
In-Reply-To: <20011004123118.49603.qmail@web11806.mail.yahoo.com>; from etienne_lorrain@yahoo.fr on Thu, Oct 04, 2001 at 02:31:18PM +0200
Hi!
> I am not speaking of DMA'ing at the refresh frequency (approx 70 times
> per second the complete video memory), just the modified 64Kb blocks,
> "once upon a while": if a single pixel is written twice, you will just
> see the latter written value on the screen - but who cares.
> Been able to DMA the complete video memory image around 5-10 times/second
> should be over the human eye sensitivity.
> Moreover this pixel will stay on the processor memory cache a lot
> longer, even without MTRR processors.
Yep, that should work. Same trick as xterm uses.
Pavel
[Of course, user *will* see you are only updating at 5fps... But it will
be way beter than current slowness.] Are you going to create a patch?
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2001-10-13 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BBC4A4E.AC6106A6@ftel.co.uk>
2001-10-04 12:31 ` specific optimizations for unaccelerated framebuffers Etienne Lorrain
2001-10-04 14:01 ` Christopher Friesen
2001-10-04 14:28 ` Etienne Lorrain
2001-10-04 22:59 ` Alex Bligh - linux-kernel
2001-10-06 0:35 ` Pavel Machek [this message]
2001-10-15 9:26 ` Etienne Lorrain
2001-10-04 8:58 Etienne Lorrain
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=20011006003547.A42@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=etienne_lorrain@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
/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).