Deutsch   English   Français   Italiano  
<vcvj0r$3co45$3@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.arch
Subject: Re: Is Intel exceptionally unsuccessful as an architecture designer?
Date: Tue, 24 Sep 2024 23:46:35 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <vcvj0r$3co45$3@dont-email.me>
References: <memo.20240913205156.19028s@jgd.cix.co.uk>
	<vcd3ds$3o6ae$2@dont-email.me>
	<2935676af968e40e7cad204d40cafdcf@www.novabbs.org>
	<vcd7pr$3op6a$3@dont-email.me> <7wCGO.45461$xO0f.1783@fx48.iad>
	<20240918190414.00005806@yahoo.com>
	<8e1aed9ce25c70cc555731140ae14eb1@www.novabbs.org>
	<vcfln9$836k$1@dont-email.me> <vcgi7p$fmaa$2@dont-email.me>
	<vcgjns$g1mt$1@dont-email.me> <vcgpqt$gndp$1@dont-email.me>
	<vcgvt0$hp5o$1@dont-email.me> <vcicol$ov66$3@dont-email.me>
	<vcj9q9$10k84$1@dont-email.me> <vckpnr$18k7r$3@dont-email.me>
	<vcuvu4$3a16j$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 25 Sep 2024 01:46:36 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="d676190ddbdcb7173a64dc657b0df900";
	logging-data="3563653"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+toT1o+VS3Exm3wOCahD+d"
User-Agent: Pan/0.160 (Toresk; )
Cancel-Lock: sha1:wjuBz7bOrAOLnCfV/qlTgUdsBHM=
Bytes: 2814

On Tue, 24 Sep 2024 13:19:32 -0500, BGB wrote:

> On 9/20/2024 4:33 PM, Lawrence D'Oliveiro wrote:
>>
>> On Fri, 20 Sep 2024 09:55:53 +0200, Terje Mathisen wrote:
>> 
>>> Lawrence D'Oliveiro wrote:
>>>>
>>>> The way I understood to do flicker-free drawing was with just two
>>>> buffers -- “double buffering”. And rather than swap the buffer
>>>> contents, you just swapped the pointers to them.
>>>>
>>> If you cannot swap the buffers with pointer updates ...
>> 
>> Surely all the good hardware is/was designed that way, with special
>> registers pointing to “current buffer” and “back buffer”, with the
>> display coming from “current buffer” while writes typically go to “back
>> buffer”. Why would you do it otherwise?
> 
> VRAM isn't free, and the older graphics hardware (before the era of 3D
> acceleration and the like) tended to only have a single framebuffer
> (except, ironically, for text modes).

But flicker-free updating requires at least two. And even the original 
1984/1985 Macintosh could manage two, and the Amiga had its clever 
“copper” which split those buffers down to individual scan lines. With the 
base-register scheme, you don’t need more than two buffers. Yet I 
frequently hear of “triple-buffering” going on, which seems unnecessary to 
me.