From mint-bounce@lists.fishpool.fi  Wed Dec  9 12:48:06 2009
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:content-type:mime-version
         :subject:from:in-reply-to:date:content-transfer-encoding:message-id
         :references:to:x-mailer;
        bh=kSuEoirqmqCqNquAJng7dde8bZL5s9fMeossl9wHCwQ=;
        b=ItAIM8lIiXy7e3ZoKCpHcCSuLVP545V3ZIxVv0wuZvettn0NWwDCQmSi1DDSj5DLv4
         yMEPhrZQdlVb4+o4kLSxXVJHd/bkc/YbFaanloBUHhmPotvhm4gnkRoYAEL8QEI1Grgs
         Ouk7Vv9ManVIBb7GAQrz5ylJ/+8oDI/THCqGM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=sbWu9EVobVCu6CCr3W76ywUvV9nRu3eJnWEkt2S6harQMS/8cnjVDbd12QYJT9AyTD
         YKAc+Zdhmj0AnNFTTiA+HQ4emZyATUwAKXC3jhtsub+MRK7SEoEG2Q7gjlpie/zltvka
         GJgH5bW8C6t32+OTXMdqsnECL4QiDsxflN6AY=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
Subject: Re: [MiNT] XaAES sources for FreeMiNT 1.16.3
From: Peter Persson <pep.fishmoose@gmail.com>
In-Reply-To: <11a6f2b10912090920v93462c2iacfd145ee9d9c235@mail.gmail.com>
Date: Wed, 9 Dec 2009 18:46:08 +0100
Message-Id: <F738A070-73F1-4685-8F1D-BCFA09F447EA@gmail.com>
References: <11a6f2b10911270646s6ceab50i915d71aeb27f6be9@mail.gmail.com> <11a6f2b10912081349x51b88c71p278c085ff9b77f2e@mail.gmail.com> <fbbaf0fb0912081736h373ac04bg94113a15fdfd5cbe@mail.gmail.com> <11a6f2b10912082333g5ede94a6t862ff00a111c970a@mail.gmail.com> <7116AF0ECE9F4F099B489E49FEE856FC@mercatus.local> <4B1FBAB0.4080607@freesbee.fr> <fbbaf0fb0912090738x465b23a3m7fe2e13652b64507@mail.gmail.com> <B0687220-956B-4962-AB9B-E6740F46ADE0@gmail.com> <11a6f2b10912090846y6d71b0er184aaff3217e97da@mail.gmail.com> <F033621C-B7C4-472E-B5C7-94B2FCBF30C2@gmail.com> <11a6f2b10912090920v93462c2iacfd145ee9d9c235@mail.gmail.com>
To: mint <mint@lists.fishpool.fi>
X-Mailer: Apple Mail (2.1077)
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: pep.fishmoose@gmail.com
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id nB9Hm5J2022016


On 9 dec 2009, at 18.20, Paul Wratt wrote:

> a "must have", but an initial start to the sequence should be the
> ability to choose a screen rez and color depth, and I think that is
> what VDI cannot do, which is what a virtual worksataion should be able
> to do.

The XBIOS video API on the CTPCI is compatible with that of the original Falcon TOS. It's also compatible with the extensions provided by the Milan XBIOS. Personally, I think this works fairly well, apart from being too hardware dependent (different calls to set colour registers on different incarnations of the shifter, for example). There is also a slight problem regarding the allocation of video RAM. There is an undocumented TOS call for this (Srealloc()), but I think it re-allocates VRAM instead of just allocating new space.

> From memory frame buffers can be redirected or re-pointed (on PCI/ISA
> hardware anyway), which will beat bliting any day.. this may be
> dependant on video mode and/or card support, I cant remember exactly,
> but I know VESA VBE can supply this sort of support.. which comes back
> to choosing a video rez, and how to do that thru VDI (current or
> new)..

Most graphics cards can specify the framebuffer base address, but it's still limited to the onboard VRAM.

-- PeP