From mint-bounce@lists.fishpool.fi Wed Dec 9 12:04:22 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=kx01VcZHrCQqx/5Pp9MxyH8JzLH4NxnacVXkpOnw8EQ=; b=gxiPUYL4VLiuxeJXoENaDdPLW8khjOqz66VFr5GfWXoA2fmNcAp5o+SWsal25eFUEP s/UnW0FOH/zwgXav3EKanWanrxYDNoP1WFDoG7cJHB95OZDV6lqvuB17+eogCmo4pgAx VcVrLBaK2AXKfcXP//RT2m27P7P9idUDAVPB8= 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=Djr39AOZLQA3YBIRddW/HhFY8PRDR6Yzyusi2u7i2+/kug6JMc85x8Ce7rt6ugdRnM p7a7N3xn6w9iWafleS36V6FDV1OfIP5gcXf2Pxf2T/7TGy3gGkbunrIyYxDtmFHEt8YZ BN+y9TyTHKdnRJbXTN7hcYbbbjts5kfgs0hw4= 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 In-Reply-To: <11a6f2b10912090846y6d71b0er184aaff3217e97da@mail.gmail.com> Date: Wed, 9 Dec 2009 18:02:21 +0100 Message-Id: References: <11a6f2b10911270646s6ceab50i915d71aeb27f6be9@mail.gmail.com> <11a6f2b10912081349x51b88c71p278c085ff9b77f2e@mail.gmail.com> <11a6f2b10912082333g5ede94a6t862ff00a111c970a@mail.gmail.com> <7116AF0ECE9F4F099B489E49FEE856FC@mercatus.local> <4B1FBAB0.4080607@freesbee.fr> <11a6f2b10912090846y6d71b0er184aaff3217e97da@mail.gmail.com> To: mint 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: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id nB9H4LvZ015398 On 9 dec 2009, at 17.46, Paul Wratt wrote: > Hope that is understandable in the context of what VDI currently does > and does not do. I get what you're talking about; this is how the VDI works. In practice, there are lots of applications where the performance penalty imposed by the VDI cannot be justified, which means people will want to access the framebuffer directly instead. This is the case with most games & demos. -- PeP