From mint-bounce@lists.fishpool.fi Wed Dec 9 12:02:38 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=m+xep9fL7DoPGYjLKAEhY8CL9Lx9RIBN+RoCrqu8uYU=; b=jMT0p2Qb0MjTUoZ7ZqpFccXvgrdneCiXC9ANpfJrUu1glxfPTq6/J7VenX8EcJ2hUU hjTuEhMoZeKdGAiWVClAPz4gDHhXTSeZgTdr73BqL7LaGtJXTRXT7se9gWd9tN3RlnOK 727hyNwDM3Qi8ph4MAr+R1/Gimt1Z4h5vqvTg= 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=iAZBJCbJ1t8LJ+VgbopZCz9Xa9919/Ej0OGwB533HDGSQuZb3l0cOpvkiZW3xUYHck dbUr6Db6AR08NgHFspPswDD9lt3fNrLMc6lFaxAZRs10aS6WiopZNHaRMihFmfTK7m9H cIWH18V1STTkjhVo4eDZwVrzdmI3z8aQwhLsQ= Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1077) Subject: Re: [MiNT] XaAES sources for FreeMiNT 1.16.3 From: Peter Persson In-Reply-To: <4B1FD68B.9010708@freesbee.fr> Date: Wed, 9 Dec 2009 17:59:30 +0100 Message-Id: <1FC79EEB-E0BB-4F7A-B44A-8D86F95653EB@gmail.com> References: <11a6f2b10911270646s6ceab50i915d71aeb27f6be9@mail.gmail.com> <11a6f2b10912081349x51b88c71p278c085ff9b77f2e@mail.gmail.com> <11a6f2b10912082333g5ede94a6t862ff00a111c970a@mail.gmail.com> <7116AF0ECE9F4F099B489E49FEE856FC@mercatus.local> <4B1FBAB0.4080607@freesbee.fr> <4B1FD68B.9010708@freesbee.fr> To: "[MiNT] Mailing-List" 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 nB9H2b5n009478 On 9 dec 2009, at 17.55, Vincent Rivière wrote: > This reminds me the DirectX API on Windows. > M$ enabled the direct access to the video memory from user programs, even for video cards who don't support this, through MMU tricks. > The pixel format depend on the actual hardware and mode, but it can be retrieved reliably (sounds familiar ?). To get decent frame rates, the application has to render something in the same format as the physical screen before blitting it to a window. The same thing applies when accessing video ram directly, except there is no overhead for blitting etc. So basically - I still don't get why applications shouldn't have access to the framebuffer, because it's really needed for games, emulators etc. -- PeP