From: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
To: Etienne Lorrain <etienne_lorrain@yahoo.fr>, linux-kernel@vger.kernel.org
Cc: Christopher Friesen <cfriesen@nortelnetworks.com>,
Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Subject: Re: specific optimizations for unaccelerated framebuffers
Date: Thu, 04 Oct 2001 23:59:56 +0100 [thread overview]
Message-ID: <308217942.1002239996@[195.224.237.69]> (raw)
In-Reply-To: <20011004142803.72199.qmail@web11806.mail.yahoo.com>
In-Reply-To: <20011004142803.72199.qmail@web11806.mail.yahoo.com>
--On Thursday, 04 October, 2001 4:28 PM +0200 Etienne Lorrain
<etienne_lorrain@yahoo.fr> wrote:
>> Since anything less than 75Hz gives me headaches, how do you propose to
>> make this work?
>
> Because there is still memory on the video board, the display stay
> at whatever refresh the video board is set up, 80 Hz if you want.
A long time ago (tm) I used this approach successfully. It
involved using an (onboard) display controller with a limited
dotclock doing large resolution high bpp displays (but at
10 to 20 Hz), capturing the digital output in offboard Video
RAM, and displaying it at 90Hz. You get some slight artefacts
but in general worked well. And here I was copying the
whole screen each time. If you only copy changed areas,
you'd ge much better results.
--
Alex Bligh
next prev parent reply other threads:[~2001-10-04 22:59 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 [this message]
2001-10-06 0:35 ` Pavel Machek
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='308217942.1002239996@[195.224.237.69]' \
--to=linux-kernel@alex.org.uk \
--cc=cfriesen@nortelnetworks.com \
--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).