From mint-bounce@lists.fishpool.fi Thu Jul 15 06:54:48 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=YbJj9sLhIi13SeFc0YDLyCBAsBIxFtmZh/cbqNcELLo=; b=i9tQWiJcf/0VOhbxsd50phnY9qzIxBEeCzUHOEcZXzR40yViRkbIZReMTUGnwPHbbN LMdVGCnIcjwG9iks9+0EbliGmFTyrAj2R8v/2VtnH5CLkd7LoRzRqdNqvxJZlVG7qYfg 4PCUt2OF6CXNzRQVbJnYBFDDn8N0/cq4pZX4g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=uRqdShlDEEztKnx99rQh3jva1Y60WsPXkEN6wEg0X2zQbeM55AYE8hSzIBSRvn7ZS3 k6TlRC6RFpUBUOGn5Knb9td+8wBxP8hdfKboxxY8HsXUBL+KRG4WIct3OUwM5txMgySq b10zgJmZe2PUXIAYwaiTe5OBf/Pgubjq03xVc= Subject: Re: [MiNT] Bit-Depth and Graphics stuff.... Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Peter Persson In-Reply-To: Date: Thu, 15 Jul 2010 12:49:46 +0200 Cc: Michael Bernstein , MiNT Mailingliste Message-Id: <1F316BAC-66EA-4E12-90ED-27F5D2D713FC@gmail.com> References: <1BCB0F08-DCCB-423A-B4E1-CCDB279C6B83@gmail.com> <6dbce3cf64caf9c3441739836652cad8-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYMXUF0BVM6XF1YSUADWl9cQw==-webmailer2@server05.webmailer.hosteurope.de> <4C34C2E4.5080909@online.no> <3847624A-0252-410C-B103-5BA7AAE195E0@gmail.com> <20100708223029.A20680@mbernstein.de> <47B6FCDC-13AA-4B15-BF8B-2A59E6E9991F@gmail.com> <20100711114630.B16224@mbernstein.de> <20100714213300.A17990@mbernstein.de> <4D2B7F5C-46D9-4C76-847F-FCC7E2CA633E@gmail.com> To: Miro Kropacek X-Mailer: Apple Mail (2.1081) 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 o6FAsl61024129 15 jul 2010 kl. 12.39 skrev Miro Kropacek: >> I have an example for you. Let's say you would port Doom to GEM. The screen is rendered to an 8-bit packed pixel surface. >> >> Now, since it's a game, it needs to be playable on a real machine. How would you solve that? > You wouldn't do it in GEM as you know it's slow ;) Nah, it's not that slow and that's the point. > Guys, I see both "camps" have good arguments but this is leading > nowhere. I ask maybe a stupid question -- it's really such hard to > extend current VDI implementation? NVDI does it (there's couple of > apps which refuse to work without NVDI/fVDI, XaAES included) and it I totally agree - but that's not what we have to work with today. > became standard after some time so nobody is wondering. Why not extend > fVDI in the same way? I don't know how VDI calls work, XBIOS offers > quite easy way how to extend its API, just add another parameter on > stack ;-) If it's possible in similar (or even easier, maybe just > changing some input parameter from <= 8 to 16 bits?) way, why not > doing it instead of thinking about various strange and system > unfriendly solutions? And the point is, it's not even system unfriendly. -- PeP